summaryrefslogtreecommitdiff
path: root/libs/gui/BufferQueueThreadState.cpp
diff options
context:
space:
mode:
author Robert Carr <racarr@google.com> 2018-12-18 15:27:58 -0800
committer Robert Carr <racarr@google.com> 2018-12-18 15:33:52 -0800
commit695d5286168bd29ddfc0ed9fa0bfcfc8da7b321d (patch)
treeb912d221f5dfd556c7e6df198a9439f63d411eb1 /libs/gui/BufferQueueThreadState.cpp
parentb67331d61b1090fd8797672858919949c8b925a3 (diff)
Ensure onHandleDestroyed drops reference before releasing lock.
onHandleDestroyed copies the layer pointer and references it in mLayersPendingRemoval, so that the final reference will be dropped from the main thread. However the current implementation is flawed. It is possible for the main thread to process mLayersPendingRemoval after we release the lock, but BEFORE we finish executing the ~LayerCleaner destructor. This would mean the last reference would again be LayerCleaner::mLayer and we would incorrectly run the d'tor on the main thread. Scheduling priority boosts to the main thread make this more likely than it may seem. Test: Boots. Existing tests pass. Change-Id: Ife247b530b67907b28b4f29f6766c2056fe49bfa
Diffstat (limited to 'libs/gui/BufferQueueThreadState.cpp')
0 files changed, 0 insertions, 0 deletions