dea20b1f34
The transaction flags were atomically read-and-cleared to determine if a transaction was needed, in the later case, mStateLock was taken to keep the current state still during the transaction. This left a small window open, where a layer could be removed after the transaction flags were checked but before the transaction was started holding the lock. In that situation eTraversalNeeded would be set but only seen during the next transaction cycle; however, because we're handling this transaction (because of another flag) it will be commited, "loosing" the information about the layer being removed -- so when the next transaction cycle due to eTraversalNeeded starts, it won't notice that layers have been removed and won't populated the ditchedLayers array. Change-Id: Iedea9e25fee8dd98a0c5bd5ad41a20fcadf75b47 |
||
|---|---|---|
| .. | ||
| DisplayHardware | ||
| tests | ||
| Android.mk | ||
| Barrier.h | ||
| clz.cpp | ||
| clz.h | ||
| GLExtensions.cpp | ||
| GLExtensions.h | ||
| Layer.cpp | ||
| Layer.h | ||
| LayerBase.cpp | ||
| LayerBase.h | ||
| LayerDim.cpp | ||
| LayerDim.h | ||
| MessageQueue.cpp | ||
| MessageQueue.h | ||
| MODULE_LICENSE_APACHE2 | ||
| SurfaceFlinger.cpp | ||
| SurfaceFlinger.h | ||
| TextureManager.cpp | ||
| TextureManager.h | ||
| Transform.cpp | ||
| Transform.h | ||