Closed
Bug 1620705
Opened 5 years ago
Closed 5 years ago
Don't send "memory-pressure" if ContentChild::mShuttingDown
Categories
(Core :: DOM: Content Processes, task, P1)
Core
DOM: Content Processes
Tracking
()
RESOLVED
FIXED
mozilla76
Tracking | Status | |
---|---|---|
firefox76 | --- | fixed |
People
(Reporter: mccr8, Assigned: mccr8)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Olli suggested this. I added code to do this for GC/CC in bug 1620623, because we already have a boolean notification, but it looks like there's other stuff we do on memory pressure.
Comment 1•5 years ago
|
||
This is a very meaningful optimization: one of the things we do when we hit a low-memory condition is to shut down the preallocated process so we don't want to make that slow by having it respond to a memory-pressure event. Additionally if/when we re-enable tab unloading we might start shutting down other content processes too in response to memory-pressure events.
Assignee | ||
Updated•5 years ago
|
Assignee: nobody → continuation
Assignee | ||
Comment 2•5 years ago
|
||
Shutting down the process is going to free more memory than anything else we
could do, so don't delay it.
Pushed by amccreight@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5481f3606f3b
Don't send "memory-pressure" if ContentChild::mShuttingDown. r=smaug
Comment 5•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox76:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla76
You need to log in
before you can comment on or make changes to this bug.
Description
•