| commit | 24dad64b89fcb4c5fbb553b7523c527309dc30fc | [log] [tgz] |
|---|---|---|
| author | Varun Shah <varunshah@google.com> | Tue Apr 30 19:07:48 2024 +0000 |
| committer | Varun Shah <varunshah@google.com> | Tue Apr 30 19:13:11 2024 +0000 |
| tree | 3e1fd3e37f38cfdbc3f9c8eae522bc923b40f7ab | |
| parent | 8727697ba31725fc3e3ebda984ea026924e74097 [diff] |
Make sure last top time is valid. In some cases, the app can start an FGS due to certain launch exemptions without the app being in the TOP state. If this is the case, the app's last TOP time will always be Long.MIN_VALUE, causing the handler to repeatedly send messages and leading to a deadlock. Fixes: 337740958 Fixes: 337701437 Test: atest CtsFgsTimeoutTestCases Change-Id: Idf303b7acfd73f46481309029816686a5161ada7