I am getting crash reports in the Google Developer Console with the abort message: "Error, cannot access an invalid/free'd bitmap here!". The below stack-trace is all I've been able to get a hold of so far. The issue is only occurring on Android 6.0 devices (marshmallow). I'm not able to reproduce the issue on any of my devices. The users' that are seeing this are unable to even open the application; it crashes before they are even presented with any visual representation of the app. Since the error involves Bitmaps, I went through my entire project looking for corrupt image files but I did not find any. Any suggestions? Thanks!
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint:'google/ryu/dragon:6.0.1/MXC89L/3084571:user/release-keys'
Revision: '0'
ABI: 'arm64'
pid: 15550, tid: 15550, name: appname >>> com.domain.appname <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: 'Error, cannot access an invalid/free'd bitmap here!'
x0 0000000000000000 x1 0000000000003cbe x2 0000000000000006 x3 0000000000000000
x4 0000000000000000 x5 0000000000000001 x6 0000000000000000 x7 0000000000000000
x8 0000000000000083 x9 000000000000003c x10 0000007fcd9a8e2c x11 0000007fcd9a8e68
x12 0000007fcd9a8d40 x13 0000000000000034 x14 0000007fcd9a8f18 x15 0000000000000000
x16 0000007b0b1996a8 x17 0000007b0b15caac x18 0000007b0b51c418 x19 0000007b0b59c0a8
x20 0000007b0b59bfe8 x21 000000000000000b x22 0000000000000006 x23 0000007b0c3f9900
x24 0000000000000000 x25 000000007081e970 x26 0000007fcd9a9928 x27 0000007fcd9a9950
x28 0000007af426d340 x29 0000007fcd9a8dd0 x30 0000007b0b15a248
sp 0000007fcd9a8dd0 pc 0000007b0b15cab4 pstate 0000000020000000
backtrace:
#00 pc 000000000006aab4 /system/lib64/libc.so (tgkill+8)
#01 pc 0000000000068244 /system/lib64/libc.so (pthread_kill+68)
#02 pc 0000000000021238 /system/lib64/libc.so (raise+28)
#03 pc 000000000001b9d8 /system/lib64/libc.so (abort+60)
#04 pc 000000000000ceec /system/lib64/libcutils.so (__android_log_assert+236)
#05 pc 00000000000e8720 /system/lib64/libandroid_runtime.so (_ZNK7android6Bitmap11assertValidEv+40)
#06 pc 00000000000e8804 /system/lib64/libandroid_runtime.so (_ZN7android6Bitmap11getSkBitmapEP8SkBitmap+20)
#07 pc 00000000000fa2b8 /system/lib64/libandroid_runtime.so
#08 pc 00000000730a6f84 /data/dalvik-cache/arm64/system#framework#boot.oat (offset 0x1eda000)
I am also seeing this stack-trace, which I would gusss is related:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/j3xlteuc/j3xlteatt:6.0.1/MMB29K/J320AUCU1APC9:user/release-keys'
Revision: '0'
ABI: 'arm'
pid: 29403, tid: 29403, name: appname >>> com.domain.appname <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: 'Error, cannot access an invalid/free'd bitmap here!'
r0 00000000 r1 000072db r2 00000006 r3 b6fb2d9c
r4 b6fb2da4 r5 b6fb2d54 r6 0000000b r7 0000010c
r8 00000000 r9 b4924500 sl 12e7a280 fp 70c321e8
ip 00000006 sp bebb7540 lr b6d11501 pc b6d138f0 cpsr 400b0010
backtrace:
#00 pc 000428f0 /system/lib/libc.so (tgkill+12)
#01 pc 000404fd /system/lib/libc.so (pthread_kill+32)
#02 pc 0001cc4b /system/lib/libc.so (raise+10)
#03 pc 00019ec9 /system/lib/libc.so (__libc_android_abort+34)
#04 pc 00017550 /system/lib/libc.so (abort+4)
#05 pc 00008723 /system/lib/libcutils.so (__android_log_assert+86)
#06 pc 00090523 /system/lib/libandroid_runtime.so (android::Bitmap::assertValid() const+18)
#07 pc 0009059f /system/lib/libandroid_runtime.so (android::Bitmap::getSkBitmap(SkBitmap*)+6)
#08 pc 00099c35 /system/lib/libandroid_runtime.so
#09 pc 033768df /system/framework/arm/boot.oat (offset 0x2f4c000)
It might crash if your bitmap calls recycle() method.
try without using yourbitmap.recycle() method.
Related
Sometimes, not always, when I open page my app crashes and I am getting error which is not giving me any clue what exactly is the problem.
How to handle this error to get info what is generating this error?
W/System (14382): ClassLoader referenced unknown path:
F/libc (14382): Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 14706 (1.ui), pid 14382 (a24.partyfinder)
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Xiaomi/beryllium/beryllium:10/QKQ1.190828.002/V12.0.3.0.QEJMIXM:user/release-keys'
Revision: '0'
ABI: 'arm64'
Timestamp: 2022-10-27 12:22:39+0200
pid: 14382, tid: 14706, name: 1.ui >>> com.lea24.partyfinder <<<
uid: 10496
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
Cause: null pointer dereference
x0 0000000000000000 x1 0000007ca35d1560 x2 0000000000000000 x3 0000007c9ccd9af8
x4 0000000000000000 x5 0000007c8ffacf38 x6 0000000000000000 x7 0000000000000004
x8 0000000000000100 x9 0000007c9932c808 x10 0000000000000000 x11 0000000000000000
x12 000000000000000d x13 0000000000001400 x14 0000000000000008 x15 aaaaaaaaaaaaaaab
x16 0000007d920ee708 x17 0000007d920e3138 x18 0000007c8f7ae000 x19 0000007d0163aaa0
x20 0000007d01778b00 x21 0000007d0163aaa0 x22 0000007d0163aaa8 x23 0000007c9c246eb8
x24 0000007b0000c581 x25 0000007c8fed9000 x26 0000007ca34c6400 x27 0000007b00011570
x28 000000080000007b x29 0000007c8ffad528
sp 0000007c8ffad080 lr 0000007c92a3ef14 pc 0000007c92a3ef14
backtrace:
#00 pc 000000000197df14 /data/app/com.lea24.partyfinder-7kEcULcMqt_ySh4qrZZW4A==/lib/arm64/libflutter.so (BuildId: 0220434562f40b7e4f4472231488d2f9c587e4f1)
#01 pc 000000000197d6c4 /data/app/com.lea24.partyfinder-7kEcULcMqt_ySh4qrZZW4A==/lib/arm64/libflutter.so (BuildId: 0220434562f40b7e4f4472231488d2f9c587e4f1)
#02 pc 000000000197d6c4 /data/app/com.lea24.partyfinder-7kEcULcMqt_ySh4qrZZW4A==/lib/arm64/libflutter.so (BuildId: 0220434562f40b7e4f4472231488d2f9c587e4f1)
#03 pc 000000000197d6c4 /data/app/com.lea24.partyfinder-7kEcULcMqt_ySh4qrZZW4A==/lib/arm64/libflutter.so (BuildId: 0220434562f40b7e4f4472231488d2f9c587e4f1)
#04 pc 000000000197d6c4 /data/app/com.lea24.partyfinder-7kEcULcMqt_ySh4qrZZW4A==/lib/arm64/libflutter.so (BuildId: 0220434562f40b7e4f4472231488d2f9c587e4f1)
#05 pc 000000000197d6c4 /data/app/com.lea24.partyfinder-7kEcULcMqt_ySh4qrZZW4A==/lib/arm64/libflutter.so (BuildId: 0220434562f40b7e4f4472231488d2f9c587e4f1)
#06 pc 000000000197d6c4 /data/app/com.lea24.partyfinder-7kEcULcMqt_ySh4qrZZW4A==/lib/arm64/libflutter.so (BuildId: 0220434562f40b7e4f4472231488d2f9c587e4f1)
#07 pc 000000000197d6c4 /data/app/com.lea24.partyfinder-7kEcULcMqt_ySh4qrZZW4A==/lib/arm64/libflutter.so (BuildId: 0220434562f40b7e4f4472231488d2f9c587e4f1)
#08 pc 000000000197d6c4 /data/app/com.lea24.partyfinder-7kEcULcMqt_ySh4qrZZW4A==/lib/arm64/libflutter.so (BuildId: 0220434562f40b7e4f4472231488d2f9c587e4f1)
#09 pc 000000000197d6c4 /data/app/com.lea24.partyfinder-7kEcULcMqt_ySh4qrZZW4A==/lib/arm64/libflutter.so (BuildId: 0220434562f40b7e4f4472231488d2f9c587e4f1)
I built a game with Unity 2020.3.37f1c1, but I've been getting some weird crashes recently.
libunity called 'EGL_ClientWaitSyncKHR' of 'libGLESv2_samsung. so', and finally crashed in /vendor/lib64/hw/vulkan.samsung.so.
Currently only appears on Samsung S22(Android 12)
The following is the wrong stack information and attachment:
Exception java.lang.Error: FATAL EXCEPTION [main]
Unity version : 2020.3.37f1c1
Device model : samsung SM-S901B
Device fingerprint: samsung/r0sxeea/r0s:12/SP1A.210812.016/S901BXXU2AVG6:user/release-keys
Build Type : Release
Scripting Backend : IL2CPP
ABI : arm64-v8a
Strip Engine Code : true
Caused by: java.lang.Error: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Version '2020.3.37f1c1 (9f30be21c416)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a'
Build fingerprint: 'samsung/r0sxeea/r0s:12/SP1A.210812.016/S901BXXU2AVG6:user/release-keys'
Revision: '28'
ABI: 'arm64'
Timestamp: 2022-08-11 16:26:01+0100
pid: 31315, tid: 31510, name: UnityMain >>> com.joy.dreams <<<
uid: 10353
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x18
Cause: null pointer dereference
x0 b40000730ca851a8 x1 0000000000000001 x2 b4000073c685e958 x3 0000000000000001
x4 0000000002faf080 x5 0000007389af81f4 x6 000000739307cd74 x7 7f7f7f7f7f7f7f7f
x8 00000072e05e5930 x9 0000000000000000 x10 000000000000148e x11 00000076d3767038
x12 00000076d3767030 x13 000000007fffffff x14 0000000000236ca0 x15 000000ff43beb615
x16 000996cc2fb00000 x17 0000000027100000 x18 0000007223726000 x19 0000000002faf080
x20 0000000000000001 x21 b4000073c685e960 x22 b40000730ca851a8 x23 00000072e05e5930
x24 b4000075d6845030 x25 00000072e05e6000 x26 0000000000000001 x27 00000000000fc000
x28 00000072e04ed000 x29 00000072e05e5950
sp 00000072e05e5930 lr 0000007393046400 pc 0000007389af5678
backtrace:
#00 pc 00000000013fc678 /vendor/lib64/hw/vulkan.samsung.so (BuildId: 3c3f650bfd63758b76be354f30896f41c5962e82)
#01 pc 00000000003f73fc /vendor/lib64/egl/libGLESv2_samsung.so (BuildId: a637a476c6448ffa)
#02 pc 00000000004229c8 /vendor/lib64/egl/libGLESv2_samsung.so (BuildId: a637a476c6448ffa)
#03 pc 000000000042d0d4 /vendor/lib64/egl/libGLESv2_samsung.so (BuildId: a637a476c6448ffa)
#04 pc 000000000042ddb8 /vendor/lib64/egl/libGLESv2_samsung.so (BuildId: a637a476c6448ffa)
#05 pc 00000000002322f4 /vendor/lib64/egl/libGLESv2_samsung.so (BuildId: a637a476c6448ffa)
#06 pc 000000000023a5fc /vendor/lib64/egl/libGLESv2_samsung.so (EGL_ClientWaitSyncKHR+128) (BuildId: a637a476c6448ffa)
#07 pc 0000000000e21048 /data/app/~~udK_hURMFPtEwbPmzROagg==/com.joy.dreams-_3gKnvwVkixqDYaLkfgxvA==/lib/arm64/libunity.so (BuildId: ccc8535e5325b0e400c5bed07b4f9a9b0b53bd60)
#08 pc 0000000000e209f0 /data/app/~~udK_hURMFPtEwbPmzROagg==/com.joy.dreams-_3gKnvwVkixqDYaLkfgxvA==/lib/arm64/libunity.so (BuildId: ccc8535e5325b0e400c5bed07b4f9a9b0b53bd60)
#09 pc 00000000000b3020 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+264) (BuildId: 1001969d8caf747bff324cbb95af4b2e)
#10 pc 000000000005288c /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 1001969d8caf747bff324cbb95af4b2e)
at vulkan
at libGLESv2_samsung
at libGLESv2_samsung
at libGLESv2_samsung
at libGLESv2_samsung
at libGLESv2_samsung
at libGLESv2_samsung.EGL_ClientWaitSyncKHR (EGL_ClientWaitSyncKHR:128)
at libunity
at libunity
at libc.__pthread_start(void*) (__pthread_start:264)
at libc.__start_thread (__start_thread:64)
In player setting -other setting, Graphic API is vulkan there? Check the Target API level/Minimum API level as well.
Hope all are safe and good.
I'm a learn of React Native.
I created my first ever mobile app using React Native expo.
I released the same for Internal testing in google play console successfully.
After I received below error,
Crashes and ANRs
Native crash
Error Issue 1 of 1 Detected on 1 device during testing
Stack trace: Native crash of com.sanMobiApp.covid19
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'google/blueline/blueline:9/PQ3A.190801.002/5670241:user/release-keys'
Revision: 'MP1.0'
ABI: 'arm64'
pid: 17696, tid: 17960, name: Thread-5 >>> com.sanMobiApp.covid19 <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: 'Cannot get a dirty matrix!'
x0 0000000000000000 x1 0000000000004628 x2 0000000000000006 x3 0000000000000008
x4 feff71647164636d x5 feff71647164636d x6 feff71647164636d x7 7f7f7f7f7f7f7f7f
x8 0000000000000083 x9 00000073aa1790a0 x10 fffffff87ffffbdf x11 0000000000000001
x12 0000000000000018 x13 ffffffffffffffff x14 ffffffffff000000 x15 ffffffffffffffff
x16 00000073aa1b32c8 x17 00000073aa0f0dcc x18 0000007308f3435a x19 0000000000004520
x20 0000000000004628 x21 0000000014b14ce0 x22 0000000014b14d10 x23 0000000014b14ce0
x24 0000000014b14790 x25 0000000013309a50 x26 0000000000000000 x27 0000000000000000
x28 0000000014b14ce0 x29 0000007308f34a90
sp 0000007308f34a50 lr 00000073aa0e594c pc 00000073aa0e5974
backtrace:
#00 pc 0000000000021974 /system/lib64/libc.so (abort+116)
#01 pc 0000000000008090 /system/lib64/liblog.so (__android_log_assert+296)
#02 pc 00000000000fedf0 /system/lib64/libandroid_runtime.so (android::android_view_RenderNode_getTransformMatrix(long, long)+120)
#03 pc 00000000003d7c88 /system/framework/arm64/boot-framework.oat (offset 0x3cd000) (android.graphics.Matrix.nPostConcat [DEDUPED]+72)
#04 pc 0000000000b7b420 /system/framework/arm64/boot-framework.oat (offset 0x3cd000) (android.view.RenderNode.getMatrix+64)
#05 pc 0000000000c70d18 /system/framework/arm64/boot-framework.oat (offset 0x3cd000) (android.view.View.getMatrix+104)
#06 pc 0000000000d35524 /system/framework/arm64/boot-framework.oat (offset 0x3cd000) (android.view.ViewGroup.getChildVisibleRect+228)
#07 pc 0000000000d35928 /system/framework/arm64/boot-framework.oat (offset 0x3cd000) (android.view.ViewGroup.getChildVisibleRect+1256)
#08 pc 0000000000d35928 /system/framework/arm64/boot-framework.oat (offset 0x3cd000) (android.view.ViewGroup.getChildVisibleRect+1256)
#09 pc 0000000000d35928 /system/framework/arm64/boot-framework.oat (offset 0x3cd000) (android.view.ViewGroup.getChildVisibleRect+1256)
#10 pc 0000000000d35928 /system/framework/arm64/boot-framework.oat (offset 0x3cd000) (android.view.ViewGroup.getChildVisibleRect+1256)
#11 pc 0000000000d35928 /system/framework/arm64/boot-framework.oat (offset 0x3cd000) (android.view.ViewGroup.getChildVisibleRect+1256)
#12 pc 0000000000057c14 /dev/ashmem/dalvik-jit-code-cache (deleted)
Can you please help me to clear this error to push to production.
THANKS IN ADVANCE
I have an Android Application that uses Cmake to compile native code into my application, and it was working great on A Pixel device running Android 7.1. I decided to upgrade my Pixel device to Oreo 8.0 and now I cannot enter the native C++ code in my app.
This is the logcat dump when it crashes:
A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
A/DEBUG: Build fingerprint: 'google/sailfish/sailfish:8.0.0/OPR3.170623.007/4286350:user/release-keys'
A/DEBUG: Revision: '0'
A/DEBUG: ABI: 'arm64'
A/DEBUG: pid: 29454, tid: 30950, name: Thread-24 >>> com.myapp.nativecppapp <<<
A/DEBUG: signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
A/DEBUG: Abort message: 'invalid pthread_t 0x727d3004f0 passed to libc'
A/DEBUG: x0 0000000000000000 x1 00000000000078e6 x2 0000000000000006 x3 0000000000000008
A/DEBUG: x4 0000000000000000 x5 0000000000000000 x6 0000000000000000 x7 0000000000000030
A/DEBUG: x8 0000000000000083 x9 222b2e8c5b032e6a x10 0000000000000000 x11 0000000000000001
A/DEBUG: x12 ffffffffffffffff x13 0000000000000001 x14 0000000000000000 x15 000849a75d18b53a
A/DEBUG: x16 00000072a8aee2f8 x17 00000072a8a905d0 x18 00000072a70fef30 x19 000000000000730e
A/DEBUG: x20 00000000000078e6 x21 0000007286081ac0 x22 000000728609b998 x23 0000007286081a88
A/DEBUG: x24 0000007286081ac4 x25 000000727d3fcee0 x26 000000727d3fceb8 x27 00000000000001cc
A/DEBUG: x28 000000727fe6b000 x29 000000727d3fcc20 x30 00000072a8a44994
A/DEBUG: sp 000000727d3fcbe0 pc 00000072a8a905d8 pstate 0000000060000000
A/DEBUG: backtrace:
A/DEBUG: #00 pc 00000000000695d8 /system/lib64/libc.so (tgkill+8)
A/DEBUG: #01 pc 000000000001d990 /system/lib64/libc.so (abort+88)
A/DEBUG: #02 pc 000000000002516c /system/lib64/libc.so (__libc_fatal+116)
A/DEBUG: #03 pc 0000000000066470 /system/lib64/libc.so (_Z23__pthread_internal_findl+164)
A/DEBUG: #04 pc 0000000000065fa8 /system/lib64/libc.so (pthread_detach+16)
A/DEBUG: #05 pc 0000000000043528 /data/app/com.myapp.nativecppapp-SwBY2G1qycu-8Vec8QIe8w==/lib/arm64/libNativeLib.so
A/DEBUG: #06 pc 000000000002a6e4 /data/app/com.myapp.nativecppapp-SwBY2G1qycu-8Vec8QIe8w==/lib/arm64/libNativeLib.so
A/DEBUG: #07 pc 0000000000052430 /data/app/com.myapp.nativecppapp-SwBY2G1qycu-8Vec8QIe8w==/lib/arm64/libNativeLib.so
A/DEBUG: #08 pc 000000000005176c /data/app/com.myapp.nativecppapp-SwBY2G1qycu-8Vec8QIe8w==/lib/arm64/libNativeLib.so
A/DEBUG: #09 pc 000000000004339c /data/app/com.myapp.nativecppapp-SwBY2G1qycu-8Vec8QIe8w==/lib/arm64/libNativeLib.so
A/DEBUG: #10 pc 0000000000065f88 /system/lib64/libc.so (_ZL15__pthread_startPv+36)
A/DEBUG: #11 pc 000000000001ed24 /system/lib64/libc.so (__start_thread+68)
Here is the Cmake code that adds the shared library
add_library(NativeLib SHARED IMPORTED)
set_property(TARGET NativeLib PROPERTY IMPORTED_LOCATION "${PROJECT_SOURCE_DIR}/NativeLib/Android/Release/${ANDROID_ABI}/libNativeLib.so")
The shared library then gets linked to the target.
As I said, this was all running flawlessly on Android 7.1 and upgrading the device to 8.0 caused this crash, is this a new bug? I did read the "Native Libraries" changes for 8.0 here https://developer.android.com/about/versions/oreo/android-8.0-changes.html.
I also ran readelf on my library and got this back, which looks okay for 8.0:
LOAD 0x000000 0x0000000000000000 0x0000000000000000 0x1b61c8 0x1b61c8 R E 0x10000
LOAD 0x1b6750 0x00000000001c6750 0x00000000001c6750 0x015fc0 0x085260 RW 0x10000
DYNAMIC 0x1c1010 0x00000000001d1010 0x00000000001d1010 0x0002c0 0x0002c0 RW 0x8
GNU_EH_FRAME 0x1871a0 0x00000000001871a0 0x00000000001871a0 0x006bac 0x006bac R 0x4
GNU_STACK 0x000000 0x0000000000000000 0x0000000000000000 0x000000 0x000000 RW 0x10
GNU_RELRO 0x1b6750 0x00000000001c6750 0x00000000001c6750 0x00b8b0 0x00b8b0 R 0x1
Any ideas? Thanks!
The problem is in __pthread_internal_find function.
Before Android 8.0, if no thread can be found in the thread list, just a nullptr is returned. However, in Android 8.0, a fatal will be made.
This is requiring more careful handling of the POSIX stuff anyway...
See the last code block in pthread_internal.cpp for reference.
I have a Live Wallpaper app that handle images.
I'm getting some crashes report in the Play Store (but not in fabric.io) with this stack trace:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/hero2ltexx/hero2lte:6.0.1/MMB29K/G935FXXU1APDN:user/release-keys'
Revision: '9'
ABI: 'arm64'
pid: 15250, tid: 15331, name: RenderThread >>> com.xxxx.xxxxx <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: 'Encountered EGL error 12291 EGL_BAD_ALLOC during rendering'
x0 0000000000000000 x1 0000000000003be3 x2 0000000000000006 x3 0000000000000000
x4 0000000000000000 x5 0000000000000001 x6 0000000000000000 x7 0000000000000000
x8 0000000000000083 x9 fefeff7e6032ce0b x10 7f7f7f7f7f7fff7f x11 0101010101010101
x12 0000000000000010 x13 0000007f6f425bdc x14 0000000000000001 x15 000000000000000f
x16 0000007f9422f568 x17 0000007f941c23b8 x18 0000007f945cf720 x19 0000007f6f426500
x20 0000007f6f426440 x21 0000000000000019 x22 0000000000000006 x23 0000007f6132f6c0
x24 0000007f6132e800 x25 0000007f614fd7b0 x26 0000000000000002 x27 0000007f70602bb0
x28 0000007f6eb58c10 x29 0000007f6f425b80 x30 0000007f941bfb54
sp 0000007f6f425b80 pc 0000007f941c23c0 pstate 0000000020000000
backtrace:
#00 pc 00000000000693c0 /system/lib64/libc.so (tgkill+8)
#01 pc 0000000000066b50 /system/lib64/libc.so (pthread_kill+68)
#02 pc 0000000000023990 /system/lib64/libc.so (raise+28)
#03 pc 000000000001e2c0 /system/lib64/libc.so (abort+60)
#04 pc 000000000000cf04 /system/lib64/libcutils.so (__android_log_assert+236)
#05 pc 000000000002be6c /system/lib64/libhwui.so
#06 pc 00000000000284f4 /system/lib64/libhwui.so
#07 pc 000000000002aa68 /system/lib64/libhwui.so
#08 pc 000000000002ef50 /system/lib64/libhwui.so (_ZN7android10uirenderer12renderthread12RenderThread10threadLoopEv+124)
#09 pc 000000000001699c /system/lib64/libutils.so (_ZN7android6Thread11_threadLoopEPv+208)
#10 pc 0000000000095110 /system/lib64/libandroid_runtime.so (_ZN7android14AndroidRuntime15javaThreadShellEPv+96)
#11 pc 00000000000161ec /system/lib64/libutils.so
#12 pc 0000000000065fa0 /system/lib64/libc.so (_ZL15__pthread_startPv+52)
#13 pc 000000000001ee6c /system/lib64/libc.so (__start_thread+16)
I cannot find many informations on internet... it seems a Samsung issue only.
I had the same issue from a service, it crash when the service get destroyed, onDestroy remove some view on the WindowManager.
The solution I found working is to remove the view using removeViewImmediate instead of removeView
#Override
public void onDestroy() {
super.onDestroy();
WindowManager windowManager = (WindowManager) getSystemService(WINDOW_SERVICE);
windowManager.removeView(view);
}
replaced by
#Override
public void onDestroy() {
super.onDestroy();
WindowManager windowManager = (WindowManager) getSystemService(WINDOW_SERVICE);
windowManager.removeViewImmediate(view);
}
https://developer.android.com/reference/android/view/WindowManager.html#removeViewImmediate(android.view.View)
Not sure why yet this solve it, the doc is light...
It only happened on Samsung device that use Android 6.0.1 (mainly S6 and S7).