Closed
Bug 1181217
Opened 10 years ago
Closed 9 years ago
Annotate MOZ_CRASH so that socorro can search for them
Categories
(Core :: MFBT, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1183355
Tracking | Status | |
---|---|---|
firefox42 | --- | affected |
People
(Reporter: milan, Unassigned)
References
Details
Getting a MOZ_CRASH in the wild may suggest we're hitting situations we should not be. In some cases, where it's an OOM, we should be OK, but in some cases we're not, and we want to find those problems before we hit the high enough crash count to notice them.
If this information is in the annotations, we would also be able to process all the "relevant" MOZ_CRASH crashes, instead of whatever statistical percentage we end up processing today.
This may very well turn into a meta bug.
![]() |
||
Comment 1•10 years ago
|
||
I think it's best to leave this bug for adding the additional annotation, and we can add further steps dependent on this one as needed.
IMHO, we should add an annotation into that macro, with a key of "MozCrash" or so and a value of the comment that is handed to that MOZ_CRASH macro.
Reporter | ||
Comment 2•10 years ago
|
||
I think that's where we should end up. I'm going to suggest we start by creating a separate one, something like MOZ_CRASH_REPORT that would do this annotation, use it in a few places and sort out the issues, get socorro/supersearch up to speed. Once we're happy with it, we can have it become MOZ_CRASH.
Comment 3•9 years ago
|
||
This is really the same as bug 1183355.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•