Closed
Bug 1723474
Opened 4 years ago
Closed 4 years ago
Flag all windows crashes with a reason set to STATUS_FATAL_MEMORY_EXHAUSTION or STATUS_NO_MEMORY as OOMs
Categories
(Socorro :: Signature, task, P2)
Socorro
Signature
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gsvelto, Assigned: willkg)
Details
Attachments
(1 file)
As per title, this is mostly stuff that's being caught by WER.
Assignee | ||
Comment 1•4 years ago
|
||
Grabbing this to do this week.
Assignee: nobody → willkg
Status: NEW → ASSIGNED
Priority: -- → P2
Assignee | ||
Comment 2•4 years ago
|
||
I couldn't find crash reports for recent Firefox versions that had a reason of STATUS_NO_MEMORY
--they all were 78 and before and don't have the WER annotation. For example: bp-c2a2b88f-3166-4cd6-8f89-6b3820210708
Here's a couple of example crash reports for STATUS_FATAL_MEMORY_EXHAUSTION
:
I'll test with those.
Assignee | ||
Comment 3•4 years ago
|
||
Assignee | ||
Comment 4•4 years ago
|
||
I need to update fx-crash-sig so it supports this OOM indicator, too.
Assignee | ||
Comment 5•4 years ago
|
||
Assignee | ||
Comment 6•4 years ago
•
|
||
I pushed this out in bug #1724703 just now. Marking as FIXED.
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•