| commit | 0ee6a0e53503fa08909af4575865c597d7243c77 | [log] [tgz] |
|---|---|---|
| author | Dmitri Plotnikov <dplotnikov@google.com> | Mon Nov 20 10:34:42 2023 -0800 |
| committer | Dmitri Plotnikov <dplotnikov@google.com> | Tue Nov 21 02:41:11 2023 +0000 |
| tree | d9943db3c51d0c6bef6e1b221bc6e1736cbefefe | |
| parent | 448c60cafd434062cc91fd2b5b5fa39ff8b77c79 [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