30a49ad4ab6f389c42c506b92f7c1550b682cacb - platform_frameworks_base

commit	30a49ad4ab6f389c42c506b92f7c1550b682cacb	[log] [tgz]
author	Michael Wachenschwanz <mwachens@google.com>	Tue Oct 17 18:46:54 2023 -0700
committer	Ioana Alexandru <aioana@google.com>	Thu Aug 22 14:16:46 2024 +0000
tree	577bc9311e75b80ba81c6bb72a6813e5523ba040
parent	fde03598c4a33ac1070dd125685e435ddbf245d8 [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
Merged-In: I399d34e1a9a19b7211413e51099721ea49efa7ad
Change-Id: I399d34e1a9a19b7211413e51099721ea49efa7ad
(cherry picked from commit 1e35d99e4a8c394fc8ea11c8e4ed797c85a2e769)

services/core/java/com/android/server/am/OomAdjuster.java[diff]
services/core/java/com/android/server/am/ProcessProviderRecord.java[diff]
services/core/java/com/android/server/am/ProcessStateRecord.java[diff]
services/tests/mockingservicestests/src/com/android/server/am/MockingOomAdjusterTests.java[diff]

4 files changed