secondlife / secondlife/viewer

Odd warning when unplugging an audio device.

Open
#6,344 0 comments 0 reactions 1 assignee View on GitHub

@maxim-productengine is already working on this.

Since Sep 18, 2026.

bug triage
Dominant language
C++
Stars
299
Forks
146
Avg merge
1d 9h
Merged PRs (30d)
88

Description

Environment

Second Life Release 26.4.0.35277930100 (64bit)
Windows 11

Full Environment

Second Life Release 26.4.0.35277930100 (64bit)
Release Notes

CPU: 12th Gen Intel(R) Core(TM) i7-12700F (2112 MHz)
Memory: 16221 MB
OS Version: Microsoft Windows 11 64-bit (Build 26200.9457)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2

Windows Graphics Driver Version: 32.0.16.1692
OpenGL Version: 4.6.0 NVIDIA 616.92

Window size: 1202x880
Font Size Adjustment: 96pt
UI Scaling: 1
Draw distance: 128m
Bandwidth: 3000kbit/s
LOD factor: 1.5
Render quality: 4
Texture memory: 12282MB
Disk cache: Max size 2150.4 MB (19.7% used)

J2C Decoder Version: KDU v8.4.1
Audio Driver Version: OpenAL, version 1.1 ALSOFT 1.24.2 / OpenAL Community / OpenAL Soft: OpenAL Soft
Dullahan: 1.26.0.202510161628
CEF: 139.0.40+g465474a+chromium-139.0.7258.139
Chromium: 139.0.7258.139
LibVLC Version: 3.0.21
Voice Server Version:

September 18 2026 10:57:10

Description

Odd warning when unplugging an audio device.

Reproduction steps
  1. Have a USB headset plugged in.
  2. Log into the viewer.
  3. Unplug the USB headset.
  4. Check the SecondLife.log

Observed: An odd warning is seen.

2026-09-18T18:47:10Z WARNING #Voice# newview/llvoicewebrtc.cpp(427) LLWebRTCVoiceClient::LogMessage : (audio_device_core_win.cc:4343): Error details: ꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪꪪ

Lines 1788 and 1799 in SecondLife.log

Expected: I'm not sure.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.