summaryrefslogtreecommitdiff
path: root/services/surfaceflinger/RegionSamplingThread.cpp
diff options
context:
space:
mode:
author chaviw <chaviw@google.com> 2019-04-11 13:09:05 -0700
committer chaviw <chaviw@google.com> 2019-04-12 15:15:19 -0700
commit8beb414c9659bb19ed0e706620ad0b222d9f9fe0 (patch)
tree28c9d4baa5826484670c9d0658694a2f204e3f68 /services/surfaceflinger/RegionSamplingThread.cpp
parent572f0aed69b358b11e60586f692f87273e8910cf (diff)
Disconnect from surface when the RenderSurface object is removed.
When a display is created, SurfaceFlinger creates a DisplayDevice object that handles connecting to the surface. This is done through the RenderSurface class. However, there's no implicit call to disconnect the surface when the DisplayDevice is removed, leaving the surface connected. This prevents the surface from behing able to get connected to to another renderer. This change adds the disconnect call in the destructor of the RenderSurface object to ensure it's disconnected when the renderer is removed. Fixes: 124415123 Test: No longer repro issue in bug Test: VirtualDisplayTest.VirtualDisplayDestroyedSurfaceReuse Test: libsurfaceflinger_unittest Test: libcompositionengine_test Change-Id: I2061e4e66c63f2b46608f599dcb31304ac8e11f5
Diffstat (limited to 'services/surfaceflinger/RegionSamplingThread.cpp')
0 files changed, 0 insertions, 0 deletions