Yesterday I had an issue where I accidentally X'd out of Fluxer whilst in a voice chat, quickly reopened and joined back and connected to the same chat again and the other two participants fluxer client crashed.
Steps to reproduce
Be in voice chat
Click X on client window
Quickly re open Fluxer and join back into the server voice chat
Status changed from Fixed to Awaiting confirmationStatusFixed→Awaiting confirmation
This was closed in a bulk cleanup before Fluxer V2 without being checked or fixed. It may work now, so it is waiting for someone to confirm whether the bug still happens.
Issue happening in my community as well. We had 5 people in the channel and one of us rejoined. It caused a user to crash, who then rejoined causing another user to crash. This created an infinite loop where it was impossible for all 5 of us to be in the channel at once.
Here's the error that pops up when crashing. Seems reloading doesn't always work and sometimes resetting app data is required according to my friends.
image
This has intermittently happened to me as well. Repro is not perfectly reproducible (the first time I wanted to generate logs, I couldn't reproduce with the same person that does generally crash me). However, today it did reproduce while running Fluxer from the command line.
Manjaro running the AppImage, see fastfetch output for high-level OS details. Log captured is:
[547632:0306/134722.216213:ERROR:third_party/webrtc/pc/sdp_offer_answer.cc:431] A BUNDLE group contains a codec collision for payload_type='111. All codecs must share the same type, encoding name, clock rate and parameters. (INVALID_PARAMETER)
Log spam that occurs. Interestingly this time it didn't happen on rejoin. I connected fresh to a voice channel that a user was in and caused the user to crash. A different user tried to join the call with me afterwards and also crashed. I didn't crash at all.
image
Me and my friend did some tests and we have concluded that this seems to occur when you change another users volume above 100%.
Error message when changing volume above 100%:
`cannot update track settings when not subscribed {trackID: 'TR_AMkQu7sW2sTPmH', enabled: true, muted: false, trackInfo: {…}}
`
Error message when getting kicked out of the voice channel:
IndexSizeError: Failed to set the 'volume' property on 'HTMLMediaElement': The volume provided (1.05669) is outside the range [0, 1].
Caused by: React ErrorBoundary IndexSizeError: Failed to set the 'volume' property on 'HTMLMediaElement': The volume provided (1.05669) is outside the range [0, 1].
at l (React.tsx:37:64)
at z (DndContext.tsx:53:29)
Reproduction steps:
Set any users volume above 100%
Either you leave and rejoin or any of the users you set to above 100% volume leaves and rejoins
Crash
It wont crash if the user that you set to above 100% is muted when they rejoin.
RexSystem1 voteeditedoriginally by @mizarc on GitHub
This latest report matches an existing ticket #49
Not sure if the first report has to do with this issue as I was unable to replicate it. Doesn't seem related to the codec collision issue either.
9 comments
Comment by Rex
Comment by @mizarc
Comment by @mizarc
559363784-50bbce04-9f04-4a34-8ba1-ec4fa04a2f25.png
587×387 | 28 kB
Comment by @Kekemui
fastfetchoutput for high-level OS details. Log captured is:fastfetch:Comment by @Wuerfel3
Comment by @mizarc
570385301-f852c58a-ccc2-454d-b6d5-23722b320568.png
816×1650 | 250 kB
Comment by @Mawkey
Error message when changing volume above 100%:
`cannot update track settings when not subscribed {trackID: 'TR_AMkQu7sW2sTPmH', enabled: true, muted: false, trackInfo: {…}} `Error message when getting kicked out of the voice channel:
Reproduction steps:
- Set any users volume above 100%
- Either you leave and rejoin or any of the users you set to above 100% volume leaves and rejoins
- Crash
It wont crash if the user that you set to above 100% is muted when they rejoin.Comment by @mizarc
Comment by @mizarc