Drop non-content process priority to IDLE when going to the background
Categories
(GeckoView Graveyard :: Sandboxing, defect)
Tracking
(firefox99 fixed)
Tracking | Status | |
---|---|---|
firefox99 | --- | fixed |
People
(Reporter: agi, Assigned: agi)
References
Details
Attachments
(1 file)
The GPU process is really cheap to restart and restarting it doesn't have side effects, so we should prioritize it lower than harder-to-restart processes like content processes when we're not actively running in foreground.
Comment 1•3 years ago
|
||
Is this already taken care of here, or is there additional work to do? Or do we want an even lower priority for the GPU process?
Assignee | ||
Comment 2•3 years ago
|
||
Oh interesting! I think we should just change that to IDLE
then. I think we didn't fully understand the meaning of those values back when the code was written.
Assignee | ||
Comment 3•3 years ago
|
||
BACKGROUND and FOREGROUND priority lead to the identical oom_adj value of 11
when the app is in the background. Because all non-content processes are
restartable without losing any state, we should prioritize them lower than the
current active tab, which will be prioritized to FOREGROUND when Bug 1753700 is
fixed.
Comment 5•3 years ago
|
||
Do you know how the BACKGROUND and FOREGROUND priority lead[s] to the identical oom_adj value of 11
, where it gets calculated or is that calculated by the Android OS?
Assignee | ||
Comment 6•3 years ago
|
||
I'm not sure yet, but this doc seems interesting: https://cs.android.com/android/platform/superproject/+/master:frameworks/base/services/core/java/com/android/server/am/OomAdjuster.md
Comment 7•3 years ago
|
||
bugherder |
Comment 8•2 years ago
|
||
Moving content process management bugs to the new GeckoView::Sandboxing component.
Updated•6 months ago
|
Description
•