After the app has been open a long time, other people's voices go silent until restart (other sounds still play) #931

Open
opened 2026-11-19 05:41:08 +00:00 by charles · 4 comments
Owner

Reported by Charles on 2026-11-19.

What happens: when the app has been open for a long period, nobody in a voice channel can be heard any more. Every other sound (notification sounds, soundboard, UI sounds) still plays. Only a restart of the app brings voices back.

Not yet known: how long 'long' is; whether it happens while staying in one call or after leaving and rejoining; whether stream audio is also silent; Linux, Windows or both; whether the speaking indicators still light up; whether others still hear the affected user.

Expected: remote voices keep playing for as long as the app runs, across any number of calls.

Reported by Charles on 2026-11-19. **What happens:** when the app has been open for a long period, nobody in a voice channel can be heard any more. Every other sound (notification sounds, soundboard, UI sounds) still plays. Only a restart of the app brings voices back. **Not yet known:** how long 'long' is; whether it happens while staying in one call or after leaving and rejoining; whether stream audio is also silent; Linux, Windows or both; whether the speaking indicators still light up; whether others still hear the affected user. **Expected:** remote voices keep playing for as long as the app runs, across any number of calls.
Author
Owner

Reporter: happens on both Linux and Windows.

Reporter: happens on both Linux and Windows.
Author
Owner

The diagnostics (#932) are in nightly 2026.1119.406. The cause is still unknown. When voices go silent again on 406 or later, the voice: lines of the log from that session are what is needed, with: does leaving and rejoining fix it, do speaking rings still show, does stream sound still play, was the PC asleep or an audio device switched, and how long the app had been open.

The diagnostics (#932) are in nightly 2026.1119.406. The cause is still unknown. When voices go silent again on 406 or later, the `voice:` lines of the log from that session are what is needed, with: does leaving and rejoining fix it, do speaking rings still show, does stream sound still play, was the PC asleep or an audio device switched, and how long the app had been open.
Author
Owner

Reproduced by Charles on nightly 2026.1119.408 (Linux), 2026-11-20, with the #932 diagnostics. New facts:

  • How to trigger: sit alone in a voice channel for a while (here 15 minutes: joined 04:46:51Z with participants=0), then someone joins (05:01:30Z, join chime plays, output device opens). Their voice is not heard.
  • The watcher fired: . So the track is subscribed and libwebrtc hands the client no audio frames; the mixer and output device are not the cause (chimes play).
  • Leaving and rejoining does NOT fix it: left at 05:03:46Z, rejoined 05:03:55Z (participants=1, new room connection), same warning for the same remote track 6 s later ().
  • Restarting the app fixes it (05:04:23Z).

So the broken state is per process and survives a new room: the shared WebRTC runtime (peer connection factory / audio device module / playout), not the room, the subscription or the audio engine.

Reproduced by Charles on nightly 2026.1119.408 (Linux), 2026-11-20, with the #932 diagnostics. New facts: - **How to trigger:** sit alone in a voice channel for a while (here 15 minutes: joined 04:46:51Z with participants=0), then someone joins (05:01:30Z, join chime plays, output device opens). Their voice is not heard. - **The watcher fired:** . So the track is subscribed and libwebrtc hands the client no audio frames; the mixer and output device are not the cause (chimes play). - **Leaving and rejoining does NOT fix it:** left at 05:03:46Z, rejoined 05:03:55Z (participants=1, new room connection), same warning for the same remote track 6 s later (). - **Restarting the app fixes it** (05:04:23Z). So the broken state is per process and survives a new room: the shared WebRTC runtime (peer connection factory / audio device module / playout), not the room, the subscription or the audio engine.
Author
Owner

Nightly 2026.1120.417 has the sharper diagnostics and the workaround of #1002: when a subscribed track gets no audio at all, the next join makes the WebRTC runtime again, so leaving and rejoining should bring voices back. The cause is still unknown; this stays open. On the next occurrence the log says whether the track was ever handed over (subscribed to an audio track), whether subscribing failed, or whether WebRTC handed it no audio.

Nightly 2026.1120.417 has the sharper diagnostics and the workaround of #1002: when a subscribed track gets no audio at all, the next join makes the WebRTC runtime again, so leaving and rejoining should bring voices back. The cause is still unknown; this stays open. On the next occurrence the log says whether the track was ever handed over (`subscribed to an audio track`), whether subscribing failed, or whether WebRTC handed it no audio.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
charles/fluxer-native#931
No description provided.