Closed Bug 1344557 Opened 3 years ago Closed 2 years ago

Crash in mozalloc_abort | abort | rtc::FatalMessage::~FatalMessage

Categories

(Core :: WebRTC, defect, P2, critical)

52 Branch
Unspecified
macOS
defect

Tracking

()

RESOLVED INCOMPLETE
Tracking Status
firefox54 --- fix-optional
firefox55 --- wontfix
firefox56 --- wontfix
firefox57 --- affected

People

(Reporter: calixte, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash, regression, Whiteboard: [clouseau])

Crash Data

This bug was filed from the Socorro interface and is 
report bp-fbd8d3c4-bdea-4248-8003-204da2170305.
=============================================================

There 2 crashes on nightly 54 with buildid 20170304030205. In analyzing the backtrace, the regression may have been introduced by patch [1] to fix bug 1337777.


[1] https://hg.mozilla.org/mozilla-central/rev?node=cfa8acce82af1ce85b4cbd8f341a4d64e9f3fa81
Flags: needinfo?(rjesup)
Whiteboard: [clouseau]
[@ webrtc::ProcessThreadImpl::RegisterModule] may also be related - it shows up in the Mac crash stats with the same build ID, but with a slightly different stack.

https://crash-stats.mozilla.com/report/index/50150b52-e79a-4ecb-a540-052c02170305
Rank: 15
Priority: -- → P1
Depends on: 1363563
So what this crash signature is about is webrtc.org code failing assertions.

The problem is this covers lots of different assertions. One example is/was bug 1363563.
Mass change P1->P2 to align with new Mozilla triage process
Priority: P1 → P2
I'm going to ask that they modify the crash-stats reporting so that it ignores rtc::FatalMessage (and looks up the stack); that will split this into N bugs
Flags: needinfo?(rjesup)
We're now reporting the source of the call to FatalMessage, so this bug is no longer useful
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.