We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Hi there,
I have an Android app with 3M+ downloads, and I get frequent 'Application Not Responding' crash reports.
When I examine these, my main thread always hangs waiting for futex in shim_glBindFramebuffer() of libMali.so
What could be causing this call to dead lock?
This is the callstack, identical in all reports. I get 15 reports per day or so.
"Thread-515" prio=5 tid=10 NATIVE
| group="main" sCount=1 dsCount=0 obj=0x41f22ff0 self=0x40f11758
| sysTid=14087 nice=0 sched=0/0 cgrp=apps handle=1550005552
| schedstat=( 0 0 0 ) utm=52 stm=13 core=1
#00 pc 0000dce0 /system/lib/libc.so (__futex_syscall3+8)
#01 pc 000121bc /system/lib/libc.so
#02 pc 000589e8 /system/lib/libMali.so
#03 pc 00066b9c /system/lib/libMali.so
#04 pc 00019464 /system/lib/libMali.so
#05 pc 00019810 /system/lib/libMali.so
#06 pc 0003b2c0 /system/lib/libMali.so (shim_glBindFramebuffer+72)
#07 pc 00033ed3 /data/data/com.steenriver.littlecrane/lib/liblittlecrane.so (android_main+178)
#08 pc 00034327 /data/data/com.steenriver.littlecrane/lib/liblittlecrane.so
#09 pc 00012e60 /system/lib/libc.so (__thread_entry+48)
#10 pc 000125b8 /system/lib/libc.so (pthread_create+172)
#11 pc 000004a4 <unknown>
at dalvik.system.NativeStart.run(Native Method)
Thanks,
Bram Stolk
Any progress on this?
thx
Hi Bram,
Sorry for delay, GDC and waiting for a Tab3 have gotten in the way somewhat. I'm still waiting on the Tab3 so decided to hunt a little harder for S3 4.2 roms, but I'm coming up with nothing on sammobile, so will try with 4.1.2 to see if I can reproduce with that.
Chris
Couldn't reproduce it on the S3 4.1.2, that just gives me a blank screen and touch events get passed to the screen the app was launched from, not the app itself. Reproduced it exactly on my CM10 SGS2 though, so will take a detailed look at that.
I've asked the driver team if there are any known workarounds for affected devices, but they are quite busy at the moment so might take a week or two.
Do you have a smaller reproducer perhaps? The driver team are asking for one to help speed things up.