Closed Bug 1388259 Opened 8 years ago Closed 4 years ago

Crash in google_breakpad::ExceptionHandler::WaitForMessage | _pthread_body

Categories

(Toolkit :: Crash Reporting, defect)

Product:
Toolkit
Component:
Crash Reporting
Platform:
Unspecified
macOS
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1731162
Tracking Flags:
Tracking Status
firefox-esr52 --- wontfix
firefox-esr60 --- wontfix
firefox56 --- wontfix
firefox57 --- wontfix
firefox58 --- wontfix
firefox59 --- wontfix
firefox64 --- wontfix
firefox65 --- wontfix
firefox66 --- wontfix

People

(Reporter: ting, Unassigned)

Details

(Keywords: crash)

Crash Data

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)
Closing because no crashes reported for 12 weeks.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
There are still some crashes so reopen it.
Status: RESOLVED → REOPENED
status-firefox58: affected → wontfix
status-firefox59: affected → wontfix
status-firefox64: --- → affected
status-firefox65: --- → affected
status-firefox66: --- → affected
status-firefox-esr60: --- → affected
Resolution: WONTFIX → ---

Duping against bug 1731162 where there's a more recent investigation (and changes that made the crash easier to understand).

Status: REOPENED → RESOLVED
Closed: 7 years ago → 4 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.