Mathias Agopian 7cc6df5957 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-06-05 14:38:23 -07:00
..
powermanager	Power manager now takes calling package name arg.	2013-05-20 16:50:10 -07:00
sensorservice	revert parts of dc5b63e40, which made gyro drift estimation unstable	2013-05-30 14:26:36 -07:00
surfaceflinger	fix a possible deadlock when removing a layer and destroying a client	2013-06-05 14:38:23 -07:00