crash in EMPTY: no crashing thread identified; no frame data available (Firefox for Android only)
Categories
(Firefox for Android :: Crash Reporting, defect, P3)
Tracking
()
People
(Reporter: snorp, Unassigned)
References
(Depends on 1 open bug)
Details
(Keywords: crash, crashreportid, topcrash)
Crash Data
Reporter | ||
Updated•9 years ago
|
Reporter | ||
Updated•9 years ago
|
Comment 3•9 years ago
|
||
Comment 5•9 years ago
|
||
Reporter | ||
Comment 6•9 years ago
|
||
Reporter | ||
Updated•9 years ago
|
Reporter | ||
Comment 8•9 years ago
|
||
Updated•9 years ago
|
Comment 9•9 years ago
|
||
Comment 10•9 years ago
|
||
Comment 11•9 years ago
|
||
Comment 12•9 years ago
|
||
Comment 13•9 years ago
|
||
Comment 14•9 years ago
|
||
Comment 15•9 years ago
|
||
Comment 16•9 years ago
|
||
Comment 17•8 years ago
|
||
Updated•8 years ago
|
Comment hidden (off-topic) |
Comment hidden (off-topic) |
Comment 20•8 years ago
|
||
Updated•8 years ago
|
Comment 21•8 years ago
|
||
Comment 22•7 years ago
|
||
Comment 23•4 years ago
|
||
Assignee | ||
Updated•4 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 24•3 years ago
|
||
The bug assignee is inactive on Bugzilla, and this bug has priority 'P2'/severity 'S2'.
:cpeterson, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 25•2 years ago
|
||
Dropping priority from P2 to P3 because this bug is not currently actionable for the Android engineering team. We're waiting for the new ARM minidump writer in bug 1689358.
Updated•2 years ago
|
Comment 26•8 months ago
•
|
||
Noting there is a pretty big jump in crashes with this signature in Nightly 132, starting last Friday in buildid 20240912092307. Maybe related to bug 1910114.
Comment hidden (me-too) |
Comment hidden (me-too) |
Comment hidden (obsolete) |
Comment hidden (me-too) |
Comment 31•7 months ago
|
||
There's no real point in posting these for now. You get these if we crash and things are in such a bad state that the crash reporting machinery can't even extract a dump. So there's no real information in the reports, and no clues about what went wrong.
This bug is about making the reporter more robust so it is better able to (hopefully) at least recover a partial report, at which point the signature would (again hopefully) point to the actual problem (and not this bug), or have some context on why we weren't even able to recover a bug.
Description
•