diff options
| author | Andrii Kulian <akulian@google.com> | 2018-05-03 16:26:25 -0700 |
|---|---|---|
| committer | Andrii Kulian <akulian@google.com> | 2018-05-03 17:34:16 -0700 |
| commit | 320e3b546f9b87c69c553326894399ea64bd34b1 (patch) | |
| tree | c078ad4cbdcd11856f5ddbc575b826dfa47af7b2 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 04e1f8e6914a2e4e14d36254ce71b97ebb2fc64d (diff) | |
Schedule local activity relaunch
If local activity relaunch is executed immediately, and if
recreate() was called from a lifecycle callback, then existing
instance of activity will be destroyed while ActivityThread may
continue using it to finish performing a transaction item.
To remove this double lifecycle loop we now schedule local activity
relaunch on client thread instead of executing it immediately.
It worked in similar way until changes in b/30060825.
Bug: 78576150
Bug: 64610483
Bug: 30060825
Test: ActivityLifecycleTests
Change-Id: Ic0cef229f2f9df0fa40066d8540c4b29da7bdc58
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions