Crash in google_breakpad::ExceptionHandler::WaitForMessage | _pthread_body

NEW
Unassigned

Status

()

Toolkit
Crash Reporting
--
critical
9 months ago
2 months ago

People

(Reporter: ting, Unassigned)

Tracking

({crash})

unspecified
Unspecified
Mac OS X
crash
Points:
---

Firefox Tracking Flags

(firefox-esr52 wontfix, firefox56 wontfix, firefox57 wontfix, firefox58 affected, firefox59 affected)

Details

(crash signature)

(Reporter)

Description

9 months ago
This bug was filed from the Socorro interface and is 
report bp-4b7c8247-5240-49a0-9ae7-acd050170808.
=============================================================
Top #3 of Nightly 20170806100257 on Mac OSX, 4 reports from 4 installations.
Less than 40 crashes a day on MacOS the past three months. I'm marking as wontfix for 57 and affected for 58.
status-firefox56: --- → wontfix
status-firefox57: --- → wontfix
status-firefox58: --- → affected
status-firefox-esr52: --- → wontfix
Flags: needinfo?(ted)
Marking 59 as affected, but volume is so low this is not something we will track.
status-firefox59: ? → affected
I'm actually sort of boggled as to what is even happening here. The minidump shows us crashing in `ExceptionHandler::WaitForMessage`, which is the background thread that waits for messages indicating we crashed and then does the actual dump writing:
https://hg.mozilla.org/releases/mozilla-release/annotate/66ffd1657af8/toolkit/crashreporter/breakpad-client/mac/handler/exception_handler.cc#l485

I poked at the minidump several times and it really does look like we crashed there. But if that's true, how did we manage to write a minidump?
Flags: needinfo?(ted)
You need to log in before you can comment on or make changes to this bug.