Open
Bug 1450993
Opened 7 years ago
Updated 7 months ago
[meta] Make low-memory detection work properly on Windows
Categories
(Core :: Memory Allocator, enhancement)
Core
Memory Allocator
Tracking
()
NEW
People
(Reporter: gsvelto, Unassigned)
References
(Depends on 1 open bug)
Details
(Keywords: meta, Whiteboard: [MemShrink:meta])
The AvailableMemoryTracker [1] is supposed to detect low-memory situations on Windows and send memory pressure events to let Firefox recover from them instead of crashing. In practice it almost never triggers, and when it does it can do more harm than good. Since it has multiple flaws I'll file specific bugs for each one and tie them to this bug for tracking.
This is rather urgent since we had a significant spike in OOM crash rate starting with Firefox 58 (see a comparison of OOM|Small crashes between 57.0.4 and 58.0.2 in [2]).
[1] https://searchfox.org/mozilla-central/rev/f5fb323246bf22a3a3b4185882a1c5d8a2c02996/xpcom/base/AvailableMemoryTracker.cpp
[2] https://crash-stats.mozilla.com/signature/?product=Firefox&platform=Windows&version=57.0.4&version=58.0.2&signature=OOM%20%7C%20small&date=%3E%3D2017-09-29T06%3A01%3A00.000Z&date=%3C2018-04-04T06%3A01%3A23.000Z#graphs
Reporter | ||
Comment 1•7 years ago
|
||
This should probable be [MemShrink:meta] but let's wait for the next triage first.
Whiteboard: [MemShrink]
Updated•7 years ago
|
Whiteboard: [MemShrink] → [MemShrink:meta]
Comment 2•4 years ago
|
||
gcp said Toshihito will work on the low memory detection for Windows so leaving a NI here.
Component: General → Memory Allocator
Flags: needinfo?(tkikuchi)
Updated•4 years ago
|
Assignee: nobody → tkikuchi
Flags: needinfo?(tkikuchi)
Comment hidden (off-topic) |
Comment 4•3 years ago
|
||
Sorry, there was a problem with the detection of inactive users. I'm reverting the change.
Assignee: nobody → tokikuc
Updated•2 years ago
|
Severity: normal → S3
Comment 5•2 years ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Assignee: tokikuc → nobody
You need to log in
before you can comment on or make changes to this bug.
Description
•