Tab crash when unplugging headset durring webrtc call

RESOLVED FIXED in Firefox 57

Status

()

Core
WebRTC: Audio/Video
P3
normal
Rank:
21
RESOLVED FIXED
9 months ago
8 months ago

People

(Reporter: ng, Unassigned)

Tracking

unspecified
mozilla57
x86_64
Mac OS X
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox57+ fixed)

Details

Attachments

(1 attachment)

(Reporter)

Description

9 months ago
This happened on a appr.tc call with audio and video. I unplugged my apple earpods and the tab crashed. I have not been able to reproduce this yet.

Socorro: https://crash-stats.mozilla.com/report/index/92974edb-7828-4743-8f60-aa9330170908
Hhmm since crash report is empty is there any chance to get logs (MediaStreamGraph:4,cubeb:4)? I know it is sporadic I am asking just in case. I will try to repro here as well.
See Also: → bug 1398788

Updated

9 months ago
Rank: 21
Priority: -- → P2
I am not able to repro. Can you please try to repro with the logs activated?
Flags: needinfo?(na-g)
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Depends on: 1399905
[Tracking Requested - why for this release]:
status-firefox57: --- → affected
tracking-firefox57: --- → ?
(Reporter)

Comment 6

9 months ago
I have tried reproducing this in 56 beta using appear.in. On the 41st plug event audio and video froze but there was no crash. After a page refresh a CubebAggregateDevice appears in the gUM audio input list. I then replugged another 59 times, and still no crash.
(Reporter)

Comment 7

9 months ago
Created attachment 8908325 [details]
fx_plug_freeze_logs.stripped.tar.gz

Logs including the freeze. My default log levels are perhaps a bit aggressive with the log levels. I stripped out all the [Socket Thread] activity to get the size down.
padenot tells me this should be fixed by bug 1399905.
Status: NEW → RESOLVED
Last Resolved: 8 months ago
status-firefox57: affected → fixed
tracking-firefox57: ? → +
Resolution: --- → FIXED
Target Milestone: --- → mozilla57
Clearing NI
Flags: needinfo?(na-g)
You need to log in before you can comment on or make changes to this bug.