Open Bug 1439854 Opened 6 years ago Updated 2 years ago

Categories

(Core :: WebRTC: Audio/Video, defect, P2)

60 Branch
x86_64
Linux
defect

Tracking

()

Tracking Status
firefox59 --- affected
firefox60 --- affected

People

(Reporter: roxana.leitan, Unassigned)

Details

Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID:20180220220044

[Affected versions]:
Nightly 60.0a1

[Affected platforms]:
Ubuntu 14.04

[Prerequisites]:
A working headset is required to run this test case. The term headset refers to a device that has headphones and a microphone.
We used USB and TRRS headsets. 
The headset is unplugged

[Steps to reproduce]:
1.Launch Nightly 60.0a1 with a new profile
2.Go to https://mozilla.github.io/webrtc-landing/gum_test.html
3.Click "Audio&Video" button
4.Select Camera and Microphone to share and click "Allow" button
5.Uncheck the "Mute" checkbox located under the video 
6.Plug the USB/TRRS headset and speak

[Expected result]:
The sound should be heard in the USB/TRRS headphones without delay 

[Actual result]:
The sound is not clear and is heard in the USB headphones with delay (~15 seconds) 

[Note]:
The issue is reproducible also on Firefox Release 58.0.2 but the delay is shorter
Summary: The sound is heard with delay → The sound is heard with delay on https://mozilla.github.io/webrtc-landing/gum_test.html
Rank: 15
Priority: -- → P2
We managed to reproduce this bug using https://web.ciscospark.com/ and making a call between two stations with two different platforms: Ubuntu 16.04 x64 and Mac OS 10.12. For mac there wasn't any problems, but when we plugged the headphones back, the sound was with about 10-15 seconds delay. The delay was present only on Ubuntu. 

I would also like to mention that on Ubuntu when the headphones were unplugged the screen froze for a short moment.
We managed to reproduce this bug on https://talky.io/, making a call between macOS 10.13 and macOS 10.12 and using Firefox 59 Beta 12.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.