diff options
| author | 2023-11-20 10:34:42 -0800 | |
|---|---|---|
| committer | 2023-11-27 22:00:51 +0000 | |
| commit | 5e3ce0ed00450e92aaf3134e896252777ab67ad8 (patch) | |
| tree | 035250f9715de5dda899b4250c49505ca8cd2c81 /api/coverage/tools | |
| parent | 23e53c1c7e035240c76c1196a0ebf1e2ed153356 (diff) | |
Fix initialization of procState counters after a failed readSummary
The code before this change assumes that `mProcStateTimeMs`
and `mProcStateScreenOffTimeMs` are either both null or both non-null.
However, if during the readSummary operation one of the two counters
is read successfully while the other fails, we end up in
an inconsistent state.
Bug: 305894439
Test: atest PowerStatsTests
Change-Id: I7928031e78d742e196750a95f6a17795b4192530
Merged-In: I7928031e78d742e196750a95f6a17795b4192530
Diffstat (limited to 'api/coverage/tools')
0 files changed, 0 insertions, 0 deletions