pianyu / 0xdroid

Automatically exported from code.google.com/p/0xdroid
0 stars 0 forks source link

libgralloc deadlock #133

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

Tried playing web browser a while, and it happens to the 
deadlock(unsynchronized) status in libgralloc. and it keeps generating logcat 
messages crazily as below. Both lock and unlock will not get success.

E/msm7k.gralloc( 1013): handle 0x143cb8 not locked
E/msm7k.gralloc( 1013): handle 0x143cb8 already locked for write
E/msm7k.gralloc( 1013): handle 0x143cb8 not locked
E/msm7k.gralloc( 1013): handle 0x143cb8 already locked for write
E/msm7k.gralloc( 1013): handle 0x143cb8 already locked for write
E/msm7k.gralloc( 1013): handle 0x143cb8 not locked

Check out the dmesg log, it keeps outputting pid exited messages as below

<3>[ 1994.236275] init: untracked pid 9363 exited
<3>[ 1997.571730] init: untracked pid 9379 exited
<3>[ 1999.782697] init: untracked pid 9388 exited
<3>[ 2001.961639] init: untracked pid 9396 exited

Original issue reported on code.google.com by jserv.tw@gmail.com on 7 Jul 2010 at 2:34

GoogleCodeExporter commented 9 years ago
Fixed in git.

reference: 
http://linuxocarina.blogspot.com/2010/06/ecliar-libgralloc-deadlock-problem.html

Original comment by jserv.tw@gmail.com on 7 Jul 2010 at 2:34