Closed
Bug 1681001
Opened 4 years ago
Closed 3 years ago
[Firefox Android] About:crashes is empty after crash
Categories
(Toolkit :: Crash Reporting, defect)
Tracking
()
RESOLVED
INVALID
Tracking | Status | |
---|---|---|
firefox85 | --- | affected |
People
(Reporter: karlcow, Unassigned)
References
()
Details
With Firefox Android 85
- Go to https://www.bose.com/en_us/products/headphones/over_ear_headphones/quietcomfort-35-wireless-ii.html#v=qc35_ii_black
- The browser should crash
- Restart it
- Type:
about:crashes
Expected:
crash window with crash report ids
Actual:
- Either you get a window with "no crash report has been sent."
- Or a java.lang.NullPointerException: contexts[6] must not be null August 26, 11:56AM blocking the full UI until you restart fully the browser.
Reporter | ||
Updated•4 years ago
|
Comment 1•4 years ago
|
||
This looks to be an OOM/ANR from a quick look. I can reproduce on a Pixel 3.
Comment 2•3 years ago
|
||
I've reproduced bug 1680999 on my phone and it is indeed an out-of-memory crash. On Android we cannot intercept OOM crashes because they're indistinguishable from regular application shutdowns (Android always kills applications, they never shut down cleanly like a desktop one would do). As such we can't intercept them and generate a regular crash report. I'm closing this bug as INVALID because of this.
It might be possible to record the event and send a crash ping instead but we'd have to investigate that.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•