Closed Bug 1166937 Opened 5 years ago Closed 5 years ago

WebRTC Audio is scratchy upon disconnect


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

38 Branch



Tracking Status
firefox38 --- wontfix
firefox38.0.5 --- wontfix
firefox39 --- wontfix
firefox40 --- affected
firefox41 --- affected
firefox42 --- fixed
firefox-esr38 --- affected
Blocking Flags:


(Reporter: cg, Unassigned)




(Keywords: regression, testcase, Whiteboard: [quality])

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.65 Safari/537.36

Steps to reproduce:

1) Connect to a phone conference bridge via WebRTC/JsSIP using the following url demo I setup for this bug report:

2) After allowing browser access to the microphone, you will connect to the conference, hear an audio message about an invalid conference ID, then be disconnected.

Actual results:

Upon Disconnect (either by the phone conference or clicking the "Disconnect" button on the page), a loud scratchy noise is heard in the WebRTC audio channel.  The sound is similar to unplugging an audio cable from a powered-on stereo system.

Expected results:

No audio should be heard upon being disconnected (by the system or clicking the button on the page).

This affects only Firefox versions 38.0 through the current 38.0.5b2 version in Linux, OSX, and Windows.  Firefox browsers < 38.0 do not have this problem and no audio is heard upon disconnect.
Component: Untriaged → WebRTC: Audio/Video
OS: Unspecified → All
Product: Firefox → Core
Hardware: Unspecified → All
See Also: → 1167066
See Also: → 1167068
Ever confirmed: true
Keywords: regression

Triggered by:
c6e50e83f7cb	Sotaro Ikeda — Bug 1133167 - Add CancelSeek call to FlushDecoding() r=cpearce,bholley
Priority: -- → P2
backlog: --- → webRTC+
Rank: 25
Whiteboard: [quality]
Flags: needinfo?(sotaro.ikeda.g)
I was just curious today and as of the nightly 42.0a1 (2015-08-06) build, the scratchy noise is no longer heard. However, the scratchy disconnect noise is still heard in 39.0.3
Looks to be fixed in 42; still there in 40 and 41.

If we know what regressed it (and what fixed it - GraphDriver changes?) we could uplift to 41 perhaps
Closed: 5 years ago
Resolution: --- → FIXED
Flags: needinfo?(sotaro.ikeda.g)
You need to log in before you can comment on or make changes to this bug.