Closed Bug 1324249 Opened 8 years ago Closed 8 years ago

Crash in mozilla::ipc::AsyncMinidumpAnalyzer::AsyncMinidumpAnalyzer

Categories

(Toolkit :: Crash Reporting, defect)

defect
Not set
critical

Tracking

()

RESOLVED FIXED
mozilla53
Tracking Status
firefox50 --- unaffected
firefox51 --- unaffected
firefox52 --- unaffected
firefox53 --- fixed

People

(Reporter: marcia, Assigned: gsvelto)

References

Details

(Keywords: crash, regression)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-900e546f-7c16-423a-b9b8-b9acc2161217.
=============================================================

Seen while looking at nightly crash stats: http://bit.ly/2gXurIn. Crashes started with 20161217030205 build. 

Regression range: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=63b447888a6469b9f6ae8f76ac5f0d7c6ea239da&tochange=34a1ab064cb5b868fa75cb74d052e978eb34d6c1

Bug 1293656? ni on [:gsvelto]
Flags: needinfo?(gsvelto)
Ouch, that MOZ_RELEASE_ASSERT() call shouldn't have been there, it should have been just a warning but apparently I forgot to get rid of it. I'll cook up a patch right away.
Flags: needinfo?(gsvelto)
Oops, wrong try run, this is the right one:

https://treeherder.mozilla.org/#/jobs?repo=try&revision=a2bcb323763107f9c6d422dd7adf0d550169bdb8

All green, so I'm landing this right away.
Assignee: nobody → gsvelto
Status: NEW → ASSIGNED
Pushed by gsvelto@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/84bf30ed2729
Do not crash if we can't get the shutdown barrier r=me
https://hg.mozilla.org/mozilla-central/rev/84bf30ed2729
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla53
Blocks: 1293656
Comment for my own info more than anything else...hit this today with 20161218030213 build, where this patch doesn't exist.
Blocks: 1328657
You need to log in before you can comment on or make changes to this bug.