Mathias Agopian e5886d9178 fix a possible deadlock when removing a layer and destroying a client ... generally the last reference to a Layer is released in commitTransaction() with mStateLock held. Layer itself only holds weak references to Client, however, ~Layer() briefly promotes this weak reference -- during that time the all other strong references to that Client go away, ~Layer is left with the last one... then hell breaks loose as ~Client is called, which in turn needs to acquire mStateLock. We fix this by holding a temporary copy of the drawing state during the transaction so that the side-effects of copying the current state into the drawing state are seen only after mStateLock has been released. Bug: 9106453 Change-Id: Ic5348ac12283500ead87286a37565e8da35f1db2		2013-08-05 14:28:46 -07:00
..
powermanager
sensorservice	fix a dead-lock in sensorservice	2013-07-12 02:08:06 -07:00
surfaceflinger	fix a possible deadlock when removing a layer and destroying a client	2013-08-05 14:28:46 -07:00