| commit | 1e35d99e4a8c394fc8ea11c8e4ed797c85a2e769 | [log] [tgz] |
|---|---|---|
| author | Michael Wachenschwanz <mwachens@google.com> | Tue Oct 17 18:46:54 2023 -0700 |
| committer | Michael Wachenschwanz <mwachens@google.com> | Tue Oct 17 18:46:54 2023 -0700 |
| tree | d29b9da55fae9a4a2f31f1c393d9cea61db0c4b9 | |
| parent | ce36021dfe5a01c29c8c43ac56d34f2f88e0bb49 [diff] |
Init some time Process stats with very negative numbers mLastTopTime was initialized as 0, meaning early on in the boot OomAdjuster would mistakenly think apps had recently been in the TOP state. Also, changed mLastProviderTime even though it had some logic (now removed) to avoid the mistake. Test: atest MockingOomAdjustertest (ideally immediatly after boot) Fixes: 300106850 Change-Id: I399d34e1a9a19b7211413e51099721ea49efa7ad