diff options
| author | Shunta Sato <Shunta.Sato@sonymobile.com> | 2016-10-12 18:35:17 +0900 |
|---|---|---|
| committer | Andrii Kulian <akulian@google.com> | 2016-12-05 12:58:25 -0800 |
| commit | 9fff53f2cb9cdd5b830ff61f174a1b356c82de51 (patch) | |
| tree | 40798b1f57f8415a5fa43e188ae1dcc8ae843e74 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 33db4b77d58a2ae81c84278e2447ab011071a622 (diff) | |
Avoid NPE around mReusedTask of ActivityStarter
Symptom:
System crash by NPE is observed on ActivityStarter
during phone boot-up.
Detail and sample:
ActivityStarter has possibility to be called itself recursively
by calling TaskRecord$performClearTaskLocked().
Then class variable of mReusedTask is initialized to null
after the call, because the recursive call isn't guarded by
synchronized block.
Then NPE crash occurs on next statement.
Solutions:
Call performClearTaskLocked() before assigning
intentActivity.task to mReusedTask.
Bug: 32361138
Test: builds, boots, Manual testing of condition in bug
Author: Shigeki Yokomichi <shigeki.x.yokomichi@sonymobile.com>
Change-Id: Iaea3e066a6f7134fcae4338ff864bb236241194c
(cherry picked from commit 0bd28e2c5f7fd7e4448ae489b425e4e5cee57f9a)
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions