Android 7 Native Crash: libc.so tgkill

前端 未结 7 2017
暗喜
暗喜 2020-12-22 15:21

I\'m seeing this native crash with the following stack trace.

This happens in Android 7.0 & 7.1 only. Nothing new has been added to the app, which has been in pr

相关标签:
7条回答
  • 2020-12-22 16:02

    I had the same issue in google play console for the same devices as you.

    In my case the issue was in TextureView with animation in separate thread with lock and unlock canvas.

    I changed TextureView animation to the invalidate-onDraw animation for 7 and 7.1 android and that helped.

    0 讨论(0)
  • 2020-12-22 16:03

    Looking at the dump you provided gives some clues:

    _ZN7android10uirenderer12renderthread12RenderThread10threadLoopEv

    This indicates that the error occurred in the UI thread.

    libhwui.so x 6

    This indicates that this is happening in the middle of some graphics/ui related code.

    libcutils.so - __android_log_assert

    This is an assert handler, so most likely some kind of assert was violated in libwhui.

    abort:

    This is the application telling the O/S to shut down "abnormally".

    raise + pthread_kill + tgkill: This is the O/S (Android) shutting down the app.

    You can see some documentation for debugging these kinds of crashes here.

    Anyway, I am afraid it is really difficult to speculate beyond this coarse and imprecise interpretation of the data you presented.

    Maybe if you caught the bug while it was attached to the Android log viewer, you would have more application specific data (or even an error message which the assert function usually puts out).

    My tip is to use something like ACRA to track down all the details pertaining to the error, or get hold of an affected device and actually reproduce it while attached to a debugger.

    Good luck!

    EDIT 2017-06-16: I just want to add some extra info courtesy comment by Fco P. Apparently Google has decided to make some changes to what native libraries are allowed to run in latest versions of Android (7.x). More details are in this link.

    0 讨论(0)
  • 2020-12-22 16:10

    Not in comments (insufficient rep).

    Of the dependencies you have listed we use:

    compile 'com.android.support:cardview-v7:25.3.1'
    compile 'com.android.support:appcompat-v7:25.3.1'
    compile 'com.android.support:support-v4:25.3.1'
    
    compile 'com.google.android.gms:play-services-maps:10.2.1'
    compile 'com.google.android.gms:play-services-location:10.2.1'
    

    different versions than yours. I have strong suspection that play-services-maps contains the bug.

    Perhaps you use map fragment in viewpager as we do and many people in issue already mentioned by Koji Matsubara (https://issuetracker.google.com/issues/37123764)

    0 讨论(0)
  • 2020-12-22 16:15

    This is reported here: https://issuetracker.google.com/issues/37123764

    To reproduce: Get an affected mode, enable developer mode, and set background activities to 0. Also enable "show background crashes".

    Then open the app, and close it again: You will see the crash.

    0 讨论(0)
  • 2020-12-22 16:17

    I am also seeing this issue in Google Play Console's crash report.

    Motorola Moto X Style | Android 7.0 (SDK 24)

    *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    pid: 0, tid: 0 >>> com.myappname<<<
    
    backtrace:
      #00  pc 000000000006b81c  /system/lib64/libc.so (tgkill+8)
      #00  pc 0000000000068cb8  /system/lib64/libc.so (pthread_kill+64)
      #00  pc 0000000000023f68  /system/lib64/libc.so (raise+24)
      #00  pc 000000000001c9ec  /system/lib64/libc.so (abort+52)
      #00  pc 0000000000010d90  /system/lib64/libcutils.so (__android_log_assert+232)
      #00  pc 0000000000031bcc  /system/lib64/libhwui.so
      #00  pc 00000000000342bc  /system/lib64/libhwui.so
      #00  pc 0000000000039988  /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderThread::threadLoop()+148)
      #00  pc 0000000000012454  /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+272)
      #00  pc 000000000009de10  /system/lib64/libandroid_runtime.so (android::AndroidRuntime::javaThreadShell(void*)+116)
      #00  pc 00000000000684c0  /system/lib64/libc.so (__pthread_start(void*)+196)
      #00  pc 000000000001dc00  /system/lib64/libc.so (__start_thread+16)
    
    0 讨论(0)
  • 2020-12-22 16:21

    I don't know, maybe this problem like ours, maybe different, because I see in dependencies have including carview. Share here hope useful for someone in future

    I also faced issue on Android 7.0 and 7.1 bellow

    03-04 23:44:51.489 2173-2173/? A/DEBUG: Abort message: 'Error: Ambient Vertex Buffer overflow!!! used 420, total 284'
    03-04 23:44:51.489 2173-2173/? A/DEBUG:     eax 00000000  ebx 0000083b  ecx 00000857  edx 00000006
    03-04 23:44:51.489 2173-2173/? A/DEBUG:     esi d19ff978  edi d19ff920
    03-04 23:44:51.489 2173-2173/? A/DEBUG:     xcs 00000023  xds 0000002b  xes 0000002b  xfs 0000006b  xss 0000002b
    03-04 23:44:51.489 2173-2173/? A/DEBUG:     eip f00a6bb9  ebp d19fee68  esp d19fee0c  flags 00000292
    03-04 23:44:51.555 2173-2173/? A/DEBUG: backtrace:
    03-04 23:44:51.555 2173-2173/? A/DEBUG:     #00 pc 00000bb9  [vdso:f00a6000] (__kernel_vsyscall+9)
    03-04 23:44:51.555 2173-2173/? A/DEBUG:     #01 pc 0007a2ec  /system/lib/libc.so (tgkill+28)
    03-04 23:44:51.555 2173-2173/? A/DEBUG:     #02 pc 00075b35  /system/lib/libc.so (pthread_kill+85)
    03-04 23:44:51.555 2173-2173/? A/DEBUG:     #03 pc 0002784a  /system/lib/libc.so (raise+42)
    03-04 23:44:51.555 2173-2173/? A/DEBUG:     #04 pc 0001ee26  /system/lib/libc.so (abort+86)
    03-04 23:44:51.555 2173-2173/? A/DEBUG:     #05 pc 0000fa65  /system/lib/libcutils.so (__android_log_assert+245)
    03-04 23:44:51.555 2173-2173/? A/DEBUG:     #06 pc 00084356  /system/lib/libhwui.so
    03-04 23:44:51.555 2173-2173/? A/DEBUG:     #07 pc 0003a5ba  /system/lib/libhwui.so
    03-04 23:44:51.555 2173-2173/? A/DEBUG:     #08 pc 00083d04  /system/lib/libhwui.so
    03-04 23:44:51.555 2173-2173/? A/DEBUG:     #09 pc 0008c5df  /system/lib/libhwui.so
    03-04 23:44:51.555 2173-2173/? A/DEBUG:     #10 pc 0008e6d8  /system/lib/libhwui.so
    03-04 23:44:51.555 2173-2173/? A/DEBUG:     #11 pc 0008e5d2  /system/lib/libhwui.so
    03-04 23:44:51.555 2173-2173/? A/DEBUG:     #12 pc 000350fe  /system/lib/libhwui.so
    03-04 23:44:51.555 2173-2173/? A/DEBUG:     #13 pc 0001201f  /system/lib/libutils.so (_ZN7android6Thread11_threadLoopEPv+207)
    03-04 23:44:51.555 2173-2173/? A/DEBUG:     #14 pc 0006e53b  /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime15javaThreadShellEPv+111)
    03-04 23:44:51.555 2173-2173/? A/DEBUG:     #15 pc 00011873  /system/lib/libutils.so (_ZN13thread_data_t10trampolineEPKS_+259)
    03-04 23:44:51.555 2173-2173/? A/DEBUG:     #16 pc 00075292  /system/lib/libc.so (_ZL15__pthread_startPv+210)
    03-04 23:44:51.555 2173-2173/? A/DEBUG:     #17 pc 0002028e  /system/lib/libc.so (__start_thread+30)
    03-04 23:44:51.555 2173-2173/? A/DEBUG:     #18 pc 0001e066  /system/lib/libc.so (__bionic_clone+70)
    

    After research and search on gooogle, I replaced cardview by Framelayout then this issue was resolved

    0 讨论(0)
提交回复
热议问题