I'm using the Superpowered SDK to do some audio playback and recording. When I press a button to start playback the app crashes with
A/DEBUG: ABI: 'arm64'
A/DEBUG: pid: 18529, tid: 18548, name: RenderThread >>> com.superpowered.example <<<
A/DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x10
A/DEBUG: x0 0000007f789f8000 x1 0000007f7409f288 x2 0000007f7d6a8a88 x3 0000000000fe502b
A/DEBUG: x4 0000000000116906 x5 0000000000000000 x6 00000a4cc0b1813f x7 0000007f789f8000
A/DEBUG: x8 000000000055655a x9 000000000055655a x10 000000000000a8c0 x11 00000000213b09a0
A/DEBUG: x12 0000000000000018 x13 ffffffffa82de1ea x14 000bb95f86000000 x15 003b9aca00000000
A/DEBUG: x16 0000007f7dadc7d8 x17 0000007f7d6a8a54 x18 0000007f78892ee8 x19 0000007f78891000
A/DEBUG: x20 0000007f7409f288 x21 0000007f78892ee8 x22 0000007f7bf4e000 x23 0000007f7bf4e000
A/DEBUG: x24 0000007f7409f288 x25 7fffffffffffffff x26 00000000ffffffff x27 0000007f7a52a9b0
A/DEBUG: x28 0000007f635331e0 x29 0000007f7409f190 x30 0000007f7bec3840
A/DEBUG: sp 0000007f7409f190 pc 0000007f7bec3850 pstate 0000000080000000
A/DEBUG: backtrace:
A/DEBUG: #00 pc 0000000000025850 /system/lib64/libhwui.so
A/DEBUG: #01 pc 0000000000026e5c /system/lib64/libhwui.so
A/DEBUG: #02 pc 0000000000026fd8 /system/lib64/libhwui.so
A/DEBUG: #03 pc 000000000002b43c /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderThread::threadLoop()+124)
A/DEBUG: #04 pc 000000000001579c /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+208)
A/DEBUG: #05 pc 00000000000903cc /system/lib64/libandroid_runtime.so (android::AndroidRuntime::javaThreadShell(void*)+96)
A/DEBUG: #06 pc 0000000000014fec /system/lib64/libutils.so
A/DEBUG: #07 pc 0000000000065fb4 /system/lib64/libc.so (__pthread_start(void*)+52)
A/DEBUG: #08 pc 000000000001ed84 /system/lib64/libc.so (__start_thread+16)
I already opened an issue on their github repo, but they won't investigate any further bacause it's obviously an error in my "custom UI code".
So after hours of debugging here is what I found:
It seems like triggering playback in the native library somehow interferes with the android internals.
Adding random delays to the button actions reduces the likelihood of a crash.
A temporary workaround was to disable hardware acceleration (android:hardwareAccelerated="false").
If you want to try it yourself you can find the code here.
Has anyone had a similiar problem? Is there any workaround that doesn't involve disabling HW acceleration? Any help is greatly appreciated!
Related
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 built AAB (for ARM & ARM-64) then test it to my Android Smartphone, but I found it crash.
By Inspecting the log I found below error (using HTC U11, API Level 26):
Build fingerprint: 'htc/ocndugl_00401/htc_ocndugl:8.0.0/OPR6.170623.013/1002308.10:user/release-keys'
Revision: '0'
ABI: 'arm64'
pid: 31372, tid: 31556, name: Loading.Preload >>> com.apps.mygame <<<
signal 5 (SIGTRAP), code -6 (SI_TKILL), fault addr --------
x0 0000000000000000 x1 0000000000007b44 x2 0000000000000005 x3 0000007dad1fe1d1
x4 000000004e524157 x5 000000004e524157 x6 000000004e524157 x7 00000000004e5241
x8 0000000000000083 x9 346b4f359488495f x10 346b4f359488495f x11 0000000000000000
x12 0000000000000000 x13 0000000000000000 x14 0000000000000000 x15 0000007e351c8000
x16 0000007e3341f2e8 x17 0000007e333c0e04 x18 0000000000000000 x19 0000007dad1fead8
x20 0000000000000000 x21 0000007e14bfc840 x22 0000007e1428c11c x23 0000007dad1ff588
x24 0000007e14c36000 x25 0000000000800101 x26 000000000014d618 x27 0000007e110ef700
x28 0000007e110ef010 x29 0000000000000008 x30 0000007e1428be84
sp 0000007dad1fea60 pc 0000007e333c0e0c pstate 0000000000000000
backtrace:
#00 pc 000000000006ae0c /system/lib64/libc.so (tgkill+8)
#01 pc 000000000064ae80 /data/app/com.apps.mygame-dztW0fQOeFKAoF2N3WRWqw==/lib/arm64/libunity.so
#02 pc 000000000064b390 /data/app/com.apps.mygame-dztW0fQOeFKAoF2N3WRWqw==/lib/arm64/libunity.so
#03 pc 000000000027fa58 /data/app/com.apps.mygame-dztW0fQOeFKAoF2N3WRWqw==/lib/arm64/libunity.so
#04 pc 000000000027fdf4 /data/app/com.apps.mygame-dztW0fQOeFKAoF2N3WRWqw==/lib/arm64/libunity.so
#05 pc 00000000003035d0 /data/app/com.apps.mygame-dztW0fQOeFKAoF2N3WRWqw==/lib/arm64/libunity.so
#06 pc 000000000030701c /data/app/com.apps.mygame-dztW0fQOeFKAoF2N3WRWqw==/lib/arm64/libunity.so
#07 pc 00000000002fff90 /data/app/com.apps.mygame-dztW0fQOeFKAoF2N3WRWqw==/lib/arm64/libunity.so
#08 pc 0000000000329b80 /data/app/com.apps.mygame-dztW0fQOeFKAoF2N3WRWqw==/lib/arm64/libunity.so
#09 pc 0000000000334628 /data/app/com.apps.mygame-dztW0fQOeFKAoF2N3WRWqw==/lib/arm64/libunity.so
#10 pc 000000000032bf00 /data/app/com.apps.mygame-dztW0fQOeFKAoF2N3WRWqw==/lib/arm64/libunity.so
#11 pc 000000000032c4e0 /data/app/com.apps.mygame-dztW0fQOeFKAoF2N3WRWqw==/lib/arm64/libunity.so
#12 pc 0000000000276b40 /data/app/com.apps.mygame-dztW0fQOeFKAoF2N3WRWqw==/lib/arm64/libunity.so
#13 pc 0000000000278488 /data/app/com.apps.mygame-dztW0fQOeFKAoF2N3WRWqw==/lib/arm64/libunity.so
#14 pc 00000000002782d4 /data/app/com.apps.mygame-dztW0fQOeFKAoF2N3WRWqw==/lib/arm64/libunity.so
#15 pc 0000000000278240 /data/app/com.apps.mygame-dztW0fQOeFKAoF2N3WRWqw==/lib/arm64/libunity.so
#16 pc 00000000002cd5b8 /data/app/com.apps.mygame-dztW0fQOeFKAoF2N3WRWqw==/lib/arm64/libunity.so
#17 pc 00000000000677a4 /system/lib64/libc.so (_ZL15__pthread_startPv+36)
#18 pc 000000000001f2a4 /system/lib64/libc.so (__start_thread+68)
I read on Unity Forum it caused by Graphic Issue so need to disable OpenGL es 3. I have tested it but still failed.
Note, I'm using below plugin (All are latest) :
Unity IAP
Google Admob
Firebase
Also, I'm using Unity 2019.3.12f1 (almost latest)
Any Idea?
I'm receiving a native crash using a shared element transition between activities, but only for Android 8.1 and on Google devices (Pixel, Pixel 2, Nexus 6P, etc...):
pid: 20499, tid: 22683, name: RenderThread >>> [APPNAME] <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: 'sp<> assignment detected data race'
x0 0000000000000000 x1 000000000000589b x2 0000000000000006 x3 0000000000000008
x4 0700007411003135 x5 0700007411003135 x6 0700007411003135 x7 3531ffffffffffff
x8 0000000000000083 x9 0000000010000000 x10 0000007214bf4ca0 x11 0000000000000001
x12 0000007214bf4dc0 x13 ffffffffffffffff x14 ffffffffffff0000 x15 ffffffffffffffff
x16 0000005c0f077fa8 x17 00000072b09c752c x18 0000000000000008 x19 0000000000005013
x20 000000000000589b x21 0000000000000083 x22 00000072249f1f40 x23 00000072249f1f58
x24 0000007214717590 x25 00000072248393a0 x26 00000072118d9220 x27 0000007214bf5350
x28 0000007214bf5300 x29 0000007214bf4ce0 x30 00000072b097c760
sp 0000007214bf4ca0 pc 00000072b097c788 pstate 0000000060000000
backtrace:
#00 pc 000000000001d788 /system/lib64/libc.so (abort+120)
#01 pc 0000000000007f08 /system/lib64/liblog.so (__android_log_assert+296)
#02 pc 0000000000010af4 /system/lib64/libutils.so (android::sp_report_race()+28)
#03 pc 00000000000fdd08 /system/lib64/libandroid_runtime.so (android::RootRenderNode::detachAnimators()+320)
#04 pc 00000000000fbcac /system/lib64/libandroid_runtime.so (android::AnimationContextBridge::destroy()+24)
#05 pc 000000000006fbd0 /system/lib64/libhwui.so (android::uirenderer::renderthread::Bridge_destroy(android::uirenderer::renderthread::destroyArgs*)+12)
#06 pc 00000000000718fc /system/lib64/libhwui.so (android::uirenderer::renderthread::MethodInvokeRenderTask::run()+24)
#07 pc 0000000000071c70 /system/lib64/libhwui.so (android::uirenderer::renderthread::SignalingRenderTask::run()+28)
#08 pc 0000000000072a58 /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderThread::threadLoop()+336)
#09 pc 0000000000011478 /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+280)
#10 pc 00000000000a9814 /system/lib64/libandroid_runtime.so (android::AndroidRuntime::javaThreadShell(void*)+140)
#11 pc 0000000000067d80 /system/lib64/libc.so (__pthread_start(void*)+36)
#12 pc 000000000001ec18 /system/lib64/libc.so (__start_thread+68)
It crashes also if the app is on background. How can I solve this? It seems to happen only if the Hardware Acceleration is enable, but I really need it enabled on my app.
I was having same issue with an AnimatedVectorDrawable set as a background of an ImageView. So basically i was showing the same animation in different rows of a recyclerview but using same object of AnimatedVectorDrawable, which lead to this crash. I solved it by creating separate objects for separate ViewHolders.
Saw the same native stack sometimes when (inadvertently) trying to restart an animation loop for an AnimatedVectorDrawable after (or perhaps while) trying to pause an Activity.
For reference, the animation loop was this:
((Animatable2)animatable).registerAnimationCallback(new Animatable2.AnimationCallback() {
#Override
public void onAnimationEnd(Drawable drawable) {
animatable.start();
}
});
When toggling away from the app, this was logged:
W/WindowManager: Unable to start animation, surface is null or no children.
Followed by a similar native stack for a race condition:
A/DEBUG: backtrace:
A/DEBUG: #00 pc 0000000000021abc /system/lib64/libc.so (abort+124)
A/DEBUG: #01 pc 00000000000080f8 /system/lib64/liblog.so (__android_log_assert+296)
A/DEBUG: #02 pc 000000000000f26c /system/lib64/libutils.so (android::sp_report_race()+28)
A/DEBUG: #03 pc 000000000010d698 /system/lib64/libandroid_runtime.so (android::RootRenderNode::detachAnimators()+320)
A/DEBUG: #04 pc 000000000010b768 /system/lib64/libandroid_runtime.so (android::AnimationContextBridge::destroy()+24)
A/DEBUG: #05 pc 00000000005d211c /system/lib64/libhwui.so (android::uirenderer::renderthread::CanvasContext::destroy()+124)
A/DEBUG: #06 pc 00000000005d5550 /system/lib64/libhwui.so (std::__1::packaged_task<void ()>::operator()()+88)
A/DEBUG: #07 pc 00000000005870b0 /system/lib64/libhwui.so (android::uirenderer::WorkQueue::process()+168)
A/DEBUG: #08 pc 00000000001fd60c /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderThread::threadLoop()+244)
A/DEBUG: #09 pc 000000000000fb80 /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+280)
A/DEBUG: #10 pc 0000000000083114 /system/lib64/libc.so (__pthread_start(void*)+36)
A/DEBUG: #11 pc 00000000000233bc /system/lib64/libc.so (__start_thread+68)
This has stopped the problem - it should have been there all along in the Activity class:
#Override
protected void onPause() {
super.onPause();
animatable.stop();
}
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).