This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Hanging app in shim_glBindFramebuffer() from libMali.so

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

Parents
  • Thanks Chris,

    Are those android version nrs you speak of?
    Google Play dashboard just lists it as 4.2. (I think it may ignore sub versions.)

    Here is a list of instances of the last few days.

    Galaxy Tab3 is listed a few times, so if you have that one lying around, try that one.

    Also of the users that emailed me: some were running stock, some were running a modified image (CM10.1), so it can occur on either.

    1. by app version
      6.1549100.0%
    2. by Android version

      Android 4.12857.1%
      Android 4.0.3 - 4.0.41326.5%
      Android 4.2816.3%
    3. by device

      Galaxy Tab3 8.0 (lt01wifi)510.2%
      nuclear-evb48.2%
      ME172V (me172v)36.1%
      Mach_Speed Trio G2 Tablet (Trio_Stealth_G2)36.1%
      nuclear-evb-rtl8723au36.1%
      g12refM1006A2SY36.1%
      MachSpeed Trio Stealth_10 Tablet (D_10AL)24.1%
      PMP3970B24.1%
      nuclear_sc3041n_ainol_novo705fc_d124.1%
      g24refem69B24.1%
      Galaxy Tab3 8.0 (lt013g)24.1%
      i-mobile i-note WiFi 1.1 (M1703)24.1%
      Y8824.1%
      Proscan PLT7777 (AMLMID710K)12.0%
      a5mid12.0%
      PROSCAN PLT8235G Tablet (MID807_K)12.0%
      NX008HD8G12.0%
      g08ref12.0%
      Zeki TBDG773 (TBDG773)12.0%
      g12refM1006RO12.0%
      Galaxy Tab2 7.0 (espressorf)12.0%
      Galaxy Note 8.0 (konawifi)12.0%
      g24refem62v312.0%
      Move712.0%
      g08refem61112.0%
      HannsPad12.0%
      Eee Pad TF101 (TF101)12.0%
Reply
  • Thanks Chris,

    Are those android version nrs you speak of?
    Google Play dashboard just lists it as 4.2. (I think it may ignore sub versions.)

    Here is a list of instances of the last few days.

    Galaxy Tab3 is listed a few times, so if you have that one lying around, try that one.

    Also of the users that emailed me: some were running stock, some were running a modified image (CM10.1), so it can occur on either.

    1. by app version
      6.1549100.0%
    2. by Android version

      Android 4.12857.1%
      Android 4.0.3 - 4.0.41326.5%
      Android 4.2816.3%
    3. by device

      Galaxy Tab3 8.0 (lt01wifi)510.2%
      nuclear-evb48.2%
      ME172V (me172v)36.1%
      Mach_Speed Trio G2 Tablet (Trio_Stealth_G2)36.1%
      nuclear-evb-rtl8723au36.1%
      g12refM1006A2SY36.1%
      MachSpeed Trio Stealth_10 Tablet (D_10AL)24.1%
      PMP3970B24.1%
      nuclear_sc3041n_ainol_novo705fc_d124.1%
      g24refem69B24.1%
      Galaxy Tab3 8.0 (lt013g)24.1%
      i-mobile i-note WiFi 1.1 (M1703)24.1%
      Y8824.1%
      Proscan PLT7777 (AMLMID710K)12.0%
      a5mid12.0%
      PROSCAN PLT8235G Tablet (MID807_K)12.0%
      NX008HD8G12.0%
      g08ref12.0%
      Zeki TBDG773 (TBDG773)12.0%
      g12refM1006RO12.0%
      Galaxy Tab2 7.0 (espressorf)12.0%
      Galaxy Note 8.0 (konawifi)12.0%
      g24refem62v312.0%
      Move712.0%
      g08refem61112.0%
      HannsPad12.0%
      Eee Pad TF101 (TF101)12.0%
Children
  • Also note: google developer console lets you filter bug reports on these android version nrs.

    As you can see, nothing more specific than 4.2.

    So I expect that all 4.2.x occurrences are lumped together.

    This means that it would not surprise me if it occurs on 4.2.anything.

    filter.png