diff options
| author | Jorim Jaggi <jjaggi@google.com> | 2017-05-09 16:27:24 +0200 |
|---|---|---|
| committer | Jorim Jaggi <jjaggi@google.com> | 2017-05-09 16:27:24 +0200 |
| commit | cb956050d5e4f7450dc8d6b362eff02455ebe264 (patch) | |
| tree | ff99a6c199c5b7e98c2b558a930171fb139c8f69 /rs/java/android/renderscript/ProgramFragmentFixedFunction.java | |
| parent | d2915725d9b8bed5daa6c8410597ce3671829218 (diff) | |
Always remove orphaned starting windows, no matter what the state
We orphaned a starting window because of the following sequence:
- Task was moved to front, thus starting window was added.
- activityPaused on Launcher was called
- In the meantime, any other activity was launched.
- When activityPause was completed, we didn't set the visibility
of the original task *not* to true. Thus, we didn't have any
signal to remove the starting window.
Note that this was more easy to repro with trampoline activities,
but in theory can also happen without trampoline activities.
We already have a way to remove orphaned starting windows so
let's reuse them independantly of the activity state.
Test: Hot launch calendar, immediately press home again. Make sure
not starting window is leaked.
Fixes: 37888853
Change-Id: Ide72c55e66a15b44a51380208bbb29dda00f7694
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions