9a14392256
When a display is disconnected, removing it from SurfaceFlinger's display list is non-atomic with removing it from the Display Manager and any in-flight transactions. So SurfaceFlinger might get a display state change transaction for a display it has already forgotten about. Just ignore these. Bug: 7288082 Change-Id: Ic27e55377f3db40fb34e3b1cd67e43297df117a2 |
||
---|---|---|
.. | ||
DisplayHardware | ||
tests | ||
Android.mk | ||
Barrier.h | ||
Client.cpp | ||
Client.h | ||
clz.cpp | ||
clz.h | ||
DdmConnection.cpp | ||
DdmConnection.h | ||
DisplayDevice.cpp | ||
DisplayDevice.h | ||
EventThread.cpp | ||
EventThread.h | ||
GLExtensions.cpp | ||
GLExtensions.h | ||
Layer.cpp | ||
Layer.h | ||
LayerBase.cpp | ||
LayerBase.h | ||
LayerDim.cpp | ||
LayerDim.h | ||
LayerScreenshot.cpp | ||
LayerScreenshot.h | ||
MessageQueue.cpp | ||
MessageQueue.h | ||
MODULE_LICENSE_APACHE2 | ||
SurfaceFlinger.cpp | ||
SurfaceFlinger.h | ||
SurfaceTextureLayer.cpp | ||
SurfaceTextureLayer.h | ||
Transform.cpp | ||
Transform.h |