diff options
| author | 2022-07-11 12:59:00 +0800 | |
|---|---|---|
| committer | 2022-07-20 04:04:56 +0000 | |
| commit | eccd6e40a27c0df728465b2fe1487ed1a5919c34 (patch) | |
| tree | e484eee9f09a33339a52d711d40eb924e6b023a8 /libs/androidfw/StringPool.cpp | |
| parent | e2137ed5b3549be1fe2beb623aba468fdc629f92 (diff) | |
Fix crash caused by accessing finishing task
In our design, there are two existing recents task at the same time. If
start new recents while finishing previous recents, there are two subtasks under recents root task, one is newly created and the other
is finishing subtask. Try to get activity from finishing subtask would
be null and cause NPE when manipulate null activity.
Append non-finishing check could ensure we get activity record from
newly created subtask instead of finishing subtask.
Test: atest CtsWindowManagerDeviceTestCases
Change-Id: I3fe8357e57c4f1afe578c696e8371874be0ed45e
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions