diff options
| author | Bryce Lee <brycelee@google.com> | 2018-02-16 14:34:32 -0800 |
|---|---|---|
| committer | Bryce Lee <brycelee@google.com> | 2018-02-23 08:32:19 -0800 |
| commit | 7ace395d65edb4764fc537ac1c9ed3c07bc72c33 (patch) | |
| tree | 6e5c08908d87f7cd77abc194234c3d4e9b58efce /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | e06975dd271a98b85fc63315211f6321b1119aee (diff) | |
Always finish activity when moving to a destroyed state.
There is a possibility that an activity will not be marked as
finishing when its state is moved to the destroying/destroyed state.
This opens up the possibility of future lifecycle actions that are
gated by the finishing flag. As a result, errant signals can be
sent to the client for a destroyed activity.
This changelist addresses the issue by limiting interaction with
ActivityRecord's state to accessors. When the state is changed to
destroyed or destroying, the activity is subsequently marked as
finished.
Bug: 71506345
Test: atest FrameworksServicesTests:com.android.server.am.ActivityRecordTests#testFinishingAfterDestroying
Test: atest FrameworksServicesTests:com.android.server.am.ActivityRecordTests#testFinishingAfterDestroyed
Change-Id: Iae8766201477103c9d632a16ecb9f6e95f796a45
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions