diff options
| author | 2022-08-26 15:47:19 +0800 | |
|---|---|---|
| committer | 2022-08-29 15:09:35 +0000 | |
| commit | 08eae598a8c46291bae58dc0bff7d8ee1637a844 (patch) | |
| tree | 77e912130818ec8ffa5a4d43eee7000f76a5d787 /libs/androidfw/StringPool.cpp | |
| parent | 6a573aec8f4a482a0c744719152cf400f1f0122b (diff) | |
Unlink death recipient which references to DisplayContent
Though the remote side (SystemUI) will unregister the recipient
when receiving display removed, it may be too late that the
DisplayContent is removed from RootWindowContainer, then WMS#
setDisplayWindowInsetsController becomes no-op and causes the
instance of DisplayContent to be leaked.
Also release windowing layer manually in case it is an additional
layer which isn't managed by WindowContainer (e.g. if the display
does not have FEATURE_WINDOWED_MAGNIFICATION). So it won't rely
on GC to release.
Bug: 240704591
Test: Create/destroy virtual display many times.
GC: adb shell 'kill -10 `pidof system_server`'
No surface of virtual display exists in:
adb shell dumpsys SurfaceFlinger grep -A 100 'Offscreen'
Change-Id: Iac84992b8eb13c4348dfca87924fb0c2fa94a5b8
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions