Closed Bug 731903 Opened 13 years ago Closed 12 years ago

Crashes don't show in about:crashes

Categories

(Firefox for Android Graveyard :: General, defect)

Product:
Firefox for Android Graveyard
Component:
General
Platform:
ARM
Android
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(blocking-fennec1.0 -)

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
blocking-fennec1.0 --- -

People

(Reporter: jwir3, Unassigned)

Details

Sometimes (about 1/3 of the time), Fennec native crashes when I try to open a link (from news, etc). However, these crashes (i.e. "the process org.mozilla.fennec stopped working", etc...) are not listed in about:crashes when I restart the browser. I am thus unsure as to whether the crashes were reported and a valid stack trace was provided.
Some of the crashes are simply not caught in breakpad, afaik. The only way to get a stacktrace is with logcat.
(In reply to Martijn Wargers [:mw22] (QA - IRC nick: mw22) from comment #1) > Some of the crashes are simply not caught in breakpad, afaik. > The only way to get a stacktrace is with logcat. So are these crashes being reported to us? It seems like there are a significant number of crashes here, and if they're not being reported as part of the mobile crash report, that seems less than ideal.
This sounds like a bug Chris filed today, bug 733434.
There's 4 types of crashes. Java crashes that breakpad catches, nonJava crashes that breakpad catches, crashes that the Android OS catches, and crashes that neither the Android OS nor breakpad catches. Comment 3 shows that there are some crashes that are being caught by breakpad but doesn't provide us good info. In the case of the Android OS catching the crashes, only the market release versions will have them reported to us via the Market info. All the ones that aren't caught otherwise will need for some manual reporting and need the logcat for us to try to understand the issue. Even then in some cases, we would need gdb (jimdb) to analyze the crash as some of those crashes might not necessarily have an easy to read crash stack. OOM crashes are the ones that I most commonly see as rebooting the OS without being caught by either breakpad nor the Android OS.
Is this a requirement for gathering the most valuable crash-feedback when this thing hits Beta?
blocking-fennec1.0: --- → ?
blocking-fennec1.0: ? → -
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.