1515462 - Discord VOIP plays sound from other users that enter VOIP after me but does not play sound from other users that are already in VOIP chat. Firefox works fine with same prefs.js file

Status: UNCONFIRMED

(SeaMonkey :: General, defect)

Description

[benl]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.5

Steps to reproduce:

I went to a discord server, entered the VOIP channel, started the music bot playing music in that channel.

Heard the music fine.

Disconnected from the VOIP channel, with the music bot still playing, and re-entered the channel.

Note: Useragent must be overridden to be exactly the same as one from Firefox, or Discord won't let Seamonkey use the VOIP channel.  Mine is:
general.useragent.override;Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0


Actual results:

No music heard, but a program, NetworkTrafficView.exe, shows a lot of data coming into Seamonkey, just like when music is heard.


Expected results:

Music should have been heard.  The problem happens every time I try.

Firefox, on the other hand, works as expected.

This exact thing certainly seems to happen with real VOIP chat users, but I haven't asked anyone to help me test it.

I have several settings changes (following ghacks etc.) so I closed seamonkey and firefox and just copied the seamonkey prefs.js file into the firefox profile.

Firefox still worked correctly.

I'm aware that default settings don't (always?) show up in prefs.js, but then these wouldn't be my settings.  A diff program shows very few differences between the prefs.js files when both browsers are closed again.

Are there any settings that could cause this that I might have missed? Like a default setting that wouldn't show up in the prefs.js file?

Also, the info at about:webrtc is different between the two browsers when in the VOIP chat, but I'm not competent to understand it and it's pretty long.

I used Seamonkey 2.49.4 from the website and 2.49.5 20181210032641.

Comment 1

[benl]

Also, I forgot, once when this happened with real users, the users I couldn't hear could still hear my mic.

Comment 2

[Rainer Bielefeld]

@Reporter:
Please contribute information (Step By Step Instruction) in accordance to Mozilla Bug writing Guidelines. Which Channel ...