Closed Bug 689778 Opened 8 years ago Closed 8 months ago

Some content crashes are not getting reported at all


(Firefox for Android Graveyard :: General, defect, critical)

Not set


(Not tracked)



(Reporter: nhirata, Unassigned)


1. go to
2. once you get a content crash (close or restart tab; it doesn't matter), go to about:crashes

Expected: content crash should be listed
Actual: content crash is not listed, no errors in console.

Mozilla/5.0 (Android; Linux armv7I; rv9.0a1) Gecko/20110927 Firefox/9.0a1 Fennec/9.0a1
Device: HTC Flyer 
OS: Android 2.3
1) if you open a new tab, the tab will not close.
2) new tabs will not go to a remote webpage
3) old tabs will close.
Is this OOMing? I think that case is a known problem. If not, I'd be interested to see what's going on.
It's probably OOMing. I get that often too. It would be nice if these would be reported in some way too (even if it means there is no useful stacktrace). It would give some statistics how many users are facing it (I know, I know, I keep repeating myself, sorry about that. This is bug 623335)
I've been seeing frequent crashes on the non-mobile Wikipedia (on the Samsung Galaxy Tab) that haven't been showing up in about:crashes.  I suppose it's plausible that it's OOM.
Interestingly, the content crash dialog we get in this case don't even has the option to send a report.
I saw frequent content crashes over the weekend while trying to look at tbpl/try and trying to zoom in and then select a build to see the logs (never actually managed to do it; content crashed many times, about:crashes showed nothing).  Droid Charge running nightly
Closing all opened bug in a graveyard component
Closed: 8 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.