Closed
Bug 623335
Opened 14 years ago
Closed 12 years ago
Breakpad should collect/detect OOM for Fennec
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(fennec-)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
fennec | - | --- |
People
(Reporter: martijn.martijn, Unassigned)
Details
I get crashes a lot of times, especially on the Droid phone. But I almost never get to see a crash report id in about:crashes. This is supposedly, because I'm experiencing OOM (out of memory) crashes. I think it is important to be able to detect and collect those crashes for Fennec too. For instance, it might give an indication how many users are hitting bug 608385. On Windows, this is supposedly working now, see bug 493779. (perhaps this bug should be filed under Toolkit->Breakpad Integration?)
Reporter | ||
Updated•14 years ago
|
OS: Windows 7 → Android
Hardware: x86 → ARM
Comment 1•14 years ago
|
||
The difference that on Android, Breakpad doesn't get called at all. The kernel kills our process with SIGKILL, which we can't handle. We can probably change things so that the chrome process, when it notices that the content process has been killed with SIGKILL, sends a crash report with all the info it can muster (but an empty minidump, since we won't have one).
Reporter | ||
Updated•14 years ago
|
tracking-fennec: --- → ?
Reporter | ||
Comment 3•12 years ago
|
||
Mass resolving XUL Fennec I filed to WORKSFORME. If someone still cares about this bug, please reopen.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•