Closed Bug 1476110 Opened 6 years ago Closed 6 years ago

WebRTC audio call crashes tab

Categories

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

63 Branch
x86_64
Windows 7
defect

Tracking

()

RESOLVED DUPLICATE of bug 1475431

People

(Reporter: kibaurufu, Assigned: achronop)

Details

(Keywords: regression)

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0 Build ID: 20180716100102 Steps to reproduce: Bug first appeared in nightly builds around July 12th. I can reproduce this in Google Hangouts for Web and Discord for Web, but it's easiest to reproduce with the webRTC demo found here https://webrtc.github.io/samples/src/content/peerconnection/audio/ Steps to Reproduce: 1. Visit WebRTC peer connection audio demo page 2. Click "call" 3. Allow microphone access for site * Running Windows 7 x64 on an AMD FX-8350 system, with 32GB of DDR3 ram, and an AMD R9 290X graphics card. * Reproducible on Windows 10 * Unable to reproduce on OS X 10.13.6 (High Sierra) Actual results: Tab crashes almost immediately after allowing microphone access. Expected results: Tab should not have crashed, and a WebRTC audio call should have been established and transmitting audio. (Apologies if there is already a bug for this, but I could not for the life of me come up with the right search terms to find it)
Assignee: nobody → achronop
Keywords: regression
Priority: -- → P1
OS: Unspecified → Windows 7
Hardware: Unspecified → x86
Hardware: x86 → x86_64
Thanks for the report. Can you please provide the crash-stat link?
Flags: needinfo?(mltomkojr)
Concerning windows we have landed the following fix around July 12th. https://github.com/kinetiknz/cubeb/commit/2968cba6474822535275225e4583c67c6aaaf2ae Paul, do you think it can be responsible for this crash?
Flags: needinfo?(padenot)
Is there somewhere besides "about:crashes" that I can find tab crash reports? Because unfortunately, "about:crashes" does not have any crash reports (submitted or not) for the tab crashes.
Flags: needinfo?(achronop)
Mike, this is going to be fixed soon, and is related to a compiler change on our end. The patch is already written. Thanks for the report and sorry for the trouble !
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Flags: needinfo?(padenot)
Flags: needinfo?(mltomkojr)
Flags: needinfo?(achronop)
Resolution: --- → DUPLICATE
Group: media-core-security
Group: media-core-security
You need to log in before you can comment on or make changes to this bug.