Closed
Bug 1712693
Opened 3 years ago
Closed 3 years ago
Re-instate grabbing memory reports when we detect a low-memory situation
Categories
(Core :: Memory Allocator, enhancement)
Tracking
()
RESOLVED
FIXED
90 Branch
| Tracking | Status | |
|---|---|---|
| firefox90 | --- | fixed |
People
(Reporter: gsvelto, Assigned: toshi)
References
Details
Attachments
(1 file)
This just occurred to me, since we've started actively measuring memory use again in bug 1711610 we might as well re-instate the code that grabbed a memory report when the low-memory condition is first detected.
This looked like this. Toshito do you have some spare cycles to tackle this?
Flags: needinfo?(tkikuchi)
|
Assignee | |
Comment 1•3 years ago
|
||
Oh, I didn't know a crash report can contain a memory report. This is cool, thank you for letting me know.
Assignee: nobody → tkikuchi
Flags: needinfo?(tkikuchi)
|
|
Assignee | |
Comment 2•3 years ago
|
||
This patch reinstate the code to call SaveMemoryReport when we enter a low-memory
situation from a normal state, which was removed by bug 1586236.
Pushed by tkikuchi@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0680fba35c80 Generate a memory report when we detect a low-memory situation. r=gsvelto
|
||
Comment 4•3 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox90:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 90 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•