Yes, it's mot safe, we also must add lock&&unlock before and after call to gralloc_alloc_buffer in function gralloc_alloc. But I guess your uncaught exception is essentially another problem, not gralloc- deadlock-related one. Can you post logcat?
On 21 ноя, 13:08, AchimNohl <[email protected]> wrote: > Hi Alexey, > > > solution is simple: just remove lock&&unlock of mutex. > > it is locked before (in the same thread), so deadlock occurs. > > this does not seem to be safe. I have tried that and got beyond the > point. But now the system crashes later with an uncaught exception in > thread 19 PID 419 in my case. It is comeing somewhere from the dvm. > Android will report a EXCEPTION IN SYSTEM PROCESS and will die. I > rather think we have to find the solution for the deadlock. > > Regards, > Achim -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
