diff options
| author | wilsonshih <wilsonshih@google.com> | 2019-03-21 17:27:02 +0800 |
|---|---|---|
| committer | wilsonshih <wilsonshih@google.com> | 2019-03-27 10:43:21 +0800 |
| commit | b72ff9c60f1b7067a09d41407e77a5eeb2fe6a8c (patch) | |
| tree | 6b679072d6bd033d2a2466338d104da2e1f3582b /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | a50d69cccce55a9de0bdb8e10400e760b3fd1edc (diff) | |
Fix WallpaperEngine object leaked during stress test.
The wallpaper engine object may not have released due to someone continuously
change wallpaper with the same component, such as image wallpaper.
In this case, server side may receive attached engine to a connection, however,
it could already detached.
Example sequence:
bind wallpaper (A) connection (C1)
detachWallpaperLocked(lastwallpaper)
lastwallpaper = A + C1
bind wallpaper (A) connection (C2)
detachWallpaperLocked(lastwallpaper = A + C1)
last = A + C2
attachEngine to C1
Then the connection C1 will never be released because it was be detached.
We can fix this by notify that WallpaperService is detached.
When it was detached, it shall destroy its engine if there is, and doesn't attach
back to WallpaperManagerService anymore.
Bug: 128974839
Test: run atest WallpaperManagerTest, then dump
adb shell dumpsys activity service com.android.systemui/com.android.systemui.ImageWallpaper
to make sure there is only one WallpaperEngine object.
Change-Id: Ifea201fe8860af11376717d344fee77182b38e54
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions