Native crash on few android devices, Unity Game - android

My unity game is crashing on few android devices. Below is the crashlytics log:
Crashed: Thread: SIGSEGV 0x0000007b60251000
#00 pc 0x4d3fc libc.so
#01 pc 0x39fcffc libil2cpp.so
#02 pc 0xb30d4c libil2cpp.so
#03 pc 0x39fd6fc libil2cpp.so
#04 pc 0xb124dc libil2cpp.so
#05 pc 0xb12524 libil2cpp.so
#06 pc 0xb124dc libil2cpp.so
#07 pc 0xb2ae20 libil2cpp.so
#08 pc 0xc7ffc libc.so
#09 pc 0xb87f44 libil2cpp.so
#10 pc 0xb6c6c libc.so
#11 pc 0x5329c libc.so
#12 pc 0xb6b30 libc.so
#13 pc 0xb2a6d0 libil2cpp.so
#14 pc 0xb87f24 libil2cpp.so
I am struggling with it from a long time. It is also affecting my game's rating on play store. If anyone know about it, please help me. Thanks.

Related

My game is crashing. The crash report is attached

I uploaded a game to the play store and the game is sometimes crashing. The reason given by the google crash report is this:
pid: 0, tid: 0 >>> com.DefaultCompany.GravitysFault <<<
backtrace:
#00 pc 000000000007ba60 /system/lib64/libc.so (tgkill+8)
#01 pc 00000000004ffec4 /data/app/com.DefaultCompany.GravitysFault-MPZSN7QrIjprfkcFvzErQA==/lib/arm64/libunity.so
#02 pc 00000000005003d4 /data/app/com.DefaultCompany.GravitysFault-MPZSN7QrIjprfkcFvzErQA==/lib/arm64/libunity.so
#03 pc 0000000000164384 /data/app/com.DefaultCompany.GravitysFault-MPZSN7QrIjprfkcFvzErQA==/lib/arm64/libunity.so
#04 pc 0000000000161e00 /data/app/com.DefaultCompany.GravitysFault-MPZSN7QrIjprfkcFvzErQA==/lib/arm64/libunity.so
#05 pc 00000000001638bc /data/app/com.DefaultCompany.GravitysFault-MPZSN7QrIjprfkcFvzErQA==/lib/arm64/libunity.so
#06 pc 000000000025cc50 /data/app/com.DefaultCompany.GravitysFault-MPZSN7QrIjprfkcFvzErQA==/lib/arm64/libunity.so
#07 pc 0000000000636278 /data/app/com.DefaultCompany.GravitysFault-MPZSN7QrIjprfkcFvzErQA==/lib/arm64/libunity.so
#08 pc 0000000000319eac /data/app/com.DefaultCompany.GravitysFault-MPZSN7QrIjprfkcFvzErQA==/lib/arm64/libunity.so
#09 pc 0000000000445424 /data/app/com.DefaultCompany.GravitysFault-MPZSN7QrIjprfkcFvzErQA==/lib/arm64/libunity.so
#10 pc 00000000005e7570 /data/app/com.DefaultCompany.GravitysFault-MPZSN7QrIjprfkcFvzErQA==/lib/arm64/libunity.so
#11 pc 00000000005ef818 /data/app/com.DefaultCompany.GravitysFault-MPZSN7QrIjprfkcFvzErQA==/lib/arm64/libunity.so
#12 pc 00000000005e6d00 /data/app/com.DefaultCompany.GravitysFault-MPZSN7QrIjprfkcFvzErQA==/lib/arm64/libunity.so
#13 pc 000000000026b790 /data/app/com.DefaultCompany.GravitysFault-MPZSN7QrIjprfkcFvzErQA==/lib/arm64/libunity.so
#14 pc 0000000000090120 /system/lib64/libc.so (__pthread_start(void*)+36)
#15 pc 0000000000023968 /system/lib64/libc.so (__start_thread+68)
Can someone please tell me what it means?
Libc.so is an Android system library, and you might be able to learn more about diagnosing libc issues here: https://source.android.com/devices/tech/debug/native-crash. You could also use ndk-stack to try to get more data out of this stacktrace: https://developer.android.com/ndk/guides/ndk-stack

strange backtrace from android debuggerd

I am confused about some backtrace dump from android debuggerd
backtrace:
#00 pc 00019d5c /system/lib/libc.so (syscall+28)
#01 pc 0001d207 /system/lib/libc.so (__futex_wait_ex(void volatile*, bool, int, bool, timespec const*)+86)
#02 pc 00064303 /system/lib/libc.so (NonPI::MutexLockWithTimeout(pthread_mutex_internal_t*, bool, timespec const*)+154)
#03 pc 006030a1 /data/app/com.xxx.xxxxx/lib/arm/libB.so (std::__ndk1::mutex::lock()+4)
#04 pc 000e63e9 /data/app/com.xxx.xxxxx/lib/arm/libA.so (A::Test1::InTest2()+28)
#05 pc 000e63bd /data/app/com.xxx.xxxxx/lib/arm/libA.so (A::Test1::InTest1()+160)
#06 pc 000637f5 /system/lib/libc.so (__pthread_start(void*)+22)
#07 pc 0001e019 /system/lib/libc.so (__start_thread+24)
I am sure that I don't dynamicly link libB.so to libA.so. but the backtrace show A::Test1::InTest2() call libB.so (std::__ndk1::mutex::lock()+4)
What is the meaning of this backtrace.

ANDROID | Native crash | signal 7 (SIGBUS), code 1 (BUS_ADRALN)

I was unable to understand what could have caused this issue. Though it refers to RegexMatcher.
Does it mean, regular expression used in app may have caused this?
I am unable to reproduce this in devices. And it doesn't look like every-time issue.
Need support to understand what backtrace suggests?
Devices where Issue is seen
Huawei honor 10 Lite (HWHRY-H), Android 9
Huawei Mate 10 Pro (HWBLA), Android 9
Huawei Mate 20 Pro (HWLYA), Android 9
Huawei P20 Pro (HWCLT), Android 9
Huawei P10 Plus (HWVKY), Android 9
Huawei FIG-LX1 (HWFIG-H), Android 9
Huawei P20 Pro (HWCLT), Android 9
**Error received from Google Play console:**
backtrace:
#00 pc 0000000000133d69 /system/lib64/libicuuc.so
#01 pc 000000000019cf58 /system/lib64/libicui18n.so (icu_60::RegexMatcher::~RegexMatcher()+48)
#02 pc 000000000019cfec /system/lib64/libicui18n.so (icu_60::RegexMatcher::~RegexMatcher()+16)
#03 pc 000000000002336c /system/lib64/libjavacore.so (Matcher_free(void*)+68)
#04 pc 0000000000094120 /system/framework/arm64/boot-core-libart.oat (java.math.NativeBN.BN_copy [DEDUPED]+160)
#05 pc 000000000018340c /system/framework/arm64/boot-core-libart.oat (libcore.util.NativeAllocationRegistry$CleanerThunk.run+76)
#06 pc 000000000040c754 /system/framework/arm64/boot.oat (sun.misc.Cleaner.clean+164)
#07 pc 00000000001daa0c /system/framework/arm64/boot.oat (java.lang.ref.ReferenceQueue.enqueueLocked+236)
#08 pc 00000000001dab2c /system/framework/arm64/boot.oat (java.lang.ref.ReferenceQueue.enqueuePending+172)
#09 pc 00000000001d7b04 /system/framework/arm64/boot-core-libart.oat (java.lang.Daemons$ReferenceQueueDaemon.runInternal+244)
#10 pc 000000000015978c /system/framework/arm64/boot-core-libart.oat (java.lang.Daemons$Daemon.run+76)
#11 pc 00000000002c1038 /system/framework/arm64/boot.oat (java.lang.Thread.run+72)
#12 pc 000000000056ef88 /system/lib64/libart.so (art_quick_invoke_stub+584)
#13 pc 00000000000d4204 /system/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*)+200)
#14 pc 0000000000472fd4 /system/lib64/libart.so (art::(anonymous namespace)::InvokeWithArgArray(art::ScopedObjectAccessAlreadyRunnable const&, art::ArtMethod*, art::(anonymous namespace)::ArgArray*, art::JValue*, char const*)+104)
#15 pc 0000000000474090 /system/lib64/libart.so (art::InvokeVirtualOrInterfaceWithJValues(art::ScopedObjectAccessAlreadyRunnable const&, _jobject*, _jmethodID*, jvalue*)+424)
#16 pc 000000000049f684 /system/lib64/libart.so (art::Thread::CreateCallback(void*)+1120)
#17 pc 0000000000083588 /system/lib64/libc.so (__pthread_start(void*)+36)
#18 pc 00000000000241dc /system/lib64/libc.so (__start_thread+68)

Native Crash tgkill+8 for MediaPlayer (Samsung Oreo 8.0)

We are seeing a weird tgkill native crash for all kinds of Samsung devices with Android Oreo 8.0.
#00 pc 000000000006b818 /system/lib64/libc.so (tgkill+8)
#01 pc 000000000001df10 /system/lib64/libc.so (abort+88)
#02 pc 0000000000007f44 /system/lib64/liblog.so (__android_log_assert+304)
#03 pc 0000000000015a94 /system/lib64/libutils.so (_ZN7android6Looper4wakeEv+192)
#04 pc 0000000000695368 /system/framework/arm64/boot-framework.oat (android.os.Binder.restoreCallingIdentity [DEDUPED]+152)
#05 pc 00000000010b04b4 /system/framework/arm64/boot-framework.oat (android.os.MessageQueue.quit+276)
#06 pc 00000000010aaff4 /system/framework/arm64/boot-framework.oat (android.os.Looper.quitSafely+68)
#07 pc 0000000000e304c8 /system/framework/arm64/boot-framework.oat (android.media.MediaPlayer$4.run+456)
#08 pc 0000000001042b60 /system/framework/arm64/boot-framework.oat (android.os.Handler.dispatchMessage+80)
#09 pc 00000000010a9d00 /system/framework/arm64/boot-framework.oat (android.os.Looper.loop+1184)
#10 pc 000000000104521c /system/framework/arm64/boot-framework.oat (android.os.HandlerThread.run+620)
#11 pc 0000000000507d84 /system/lib64/libart.so (art_quick_invoke_stub+580)
#12 pc 00000000000d82f4 /system/lib64/libart.so (_ZN3art9ArtMethod6InvokeEPNS_6ThreadEPjjPNS_6JValueEPKc+200)
#13 pc 00000000004309cc /system/lib64/libart.so (_ZN3artL18InvokeWithArgArrayERKNS_33ScopedObjectAccessAlreadyRunnableEPNS_9ArtMethodEPNS_8ArgArrayEPNS_6JValueEPKc+104)
#14 pc 0000000000431b58 /system/lib64/libart.so (_ZN3art35InvokeVirtualOrInterfaceWithJValuesERKNS_33ScopedObjectAccessAlreadyRunnableEP8_jobjectP10_jmethodIDP6jvalue+432)
#15 pc 0000000000458038 /system/lib64/libart.so (_ZN3art6Thread14CreateCallbackEPv+1140)
#16 pc 0000000000068194 /system/lib64/libc.so (_ZL15__pthread_startPv+36)
#17 pc 000000000001f664 /system/lib64/libc.so (__start_thread+68)
We are using the MediaPlayer, so maybe this makes sense: android.media.MediaPlayer$4.run+456
The thing is, we have no idea how to debug it. Any ideas on what this crash is really about?
(Trying to get a Samsung with 8.0 in the meantime)
Maybe this is relevant:
tgkill - native error on Android 8.0 Samsung S8
Basically its EditText messing up on rotate for android 8.

Marshmallow crash in tgkill

This crash just occurs on Android API 23 or version 6.0, and I don't have any idea how to fix this issue?
Here's the crash report :
#00 pc 000000000006ab74 /system/lib64/libc.so (tgkill+8)
#01 pc 0000000000068304 /system/lib64/libc.so (pthread_kill+68)
#02 pc 00000000000212f8 /system/lib64/libc.so (raise+28)
#03 pc 000000000001ba98 /system/lib64/libc.so (abort+60)
#04 pc 0000000000435798 /system/lib64/libart.so (_ZN3art7Runtime5AbortEv+324)
#05 pc 0000000000139264 /system/lib64/libart.so (_ZN3art10LogMessageD2Ev+3136)
#06 pc 00000000003109cc /system/lib64/libart.so (_ZN3art9JavaVMExt8JniAbortEPKcS2_+2084)
#07 pc 0000000000310f68 /system/lib64/libart.so (_ZN3art9JavaVMExt9JniAbortFEPKcS2_z+224)
#08 pc 0000000000351ca4 /system/lib64/libart.so (_ZN3art3JNI15CallVoidMethodVEP7_JNIEnvP8_jobjectP10_jmethodIDSt9__va_list+616)
#09 pc 00000000000963cc /system/lib64/libandroid_runtime.so
#10 pc 0000000073b78ba4 /data/dalvik-cache/arm64/system#framework#boot.oat
It happened when using support library 26.x.x , Any help will be much appreciated.

Categories

Resources