| commit | 0bf67325f99bb202a6a2a99b37d0f78d4c2a276b | [log] [tgz] |
|---|---|---|
| author | Michael Wachenschwanz <mwachens@google.com> | Wed Oct 18 16:41:20 2023 +0000 |
| committer | Android Build Cherrypicker Worker <android-build-cherrypicker-worker@google.com> | Wed Oct 18 16:41:20 2023 +0000 |
| tree | d150862288a802f7c60c845ce7050d7950a82023 | |
| parent | 6a63d356f561f05f0df388f3aed487c4bbeb8f37 [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 (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:1e35d99e4a8c394fc8ea11c8e4ed797c85a2e769) Merged-In: I399d34e1a9a19b7211413e51099721ea49efa7ad Change-Id: I399d34e1a9a19b7211413e51099721ea49efa7ad