diff options
| author | 2024-08-27 14:58:39 +0000 | |
|---|---|---|
| committer | 2024-08-27 14:58:39 +0000 | |
| commit | c4ce739e0e4ef38f58edf80ca8ce35152bad42a9 (patch) | |
| tree | b3179633411fd9166138c86ca295a3be359522d6 /libs/androidfw/StringPool.cpp | |
| parent | cecce4149d07573cffe388d728485c610c9261e8 (diff) | |
Fix prev expire flow in OomAdjuster.
When an app is sent to background, it gets prev oom score with all its
bindings (except the ones bound with the BIND_WAIVE_PRIORITY flag).
Then there are three ways the app loses this prev score.
1. Another app comes top, and then goes background,
taking away the prev status.
2. After 60 seconds, prev status expires.
3. App comes foreground again. (This one is not relevant to the topic)
Flow 1 and 2 have different results. When 1 happens, all the processes
get chh+X with respect to their position in the process LRU list. But
when 2 happens, the processes with prev score all get cch. And this
causes a random killing order in LMKD.
This CL makes "prev expire" flow similar to "another app grabbing prev"
flow.
Bug: 357844136
Change-Id: I9efa3b3855d8d9ddb29d9b3358cb648d38099204
Test: atest MockingOomAdjusterTests#testUpdateOomAdj_DoAll_PreviousApp
Flag: EXEMPT bugfix
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions