Closed Bug 1344557 Opened 3 years ago Closed 2 years ago
Crash in mozalloc
_abort | abort | rtc::Fatal Message::~Fatal Message
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  to fix bug 1337777.  https://hg.mozilla.org/mozilla-central/rev?node=cfa8acce82af1ce85b4cbd8f341a4d64e9f3fa81
[@ 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
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
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.