-
Notifications
You must be signed in to change notification settings - Fork 24.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android: Crash on app launch (react-native 0.31) #9477
Comments
we can produce frequently . sounds it raised more at samsung phone? The Stack09-09 18:05:00.851: A/libc(479): Fatal signal 6 (SIGABRT), code -6 in tid 532 (mqt_js) |
@facebook-github-bot label Icebox |
Hi there! This issue is being closed because it has been inactive for a while. But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/android-crash-on-app-launch-react-native-031- ProductPains helps the community prioritize the most important issues thanks to its voting feature. Also, if this issue is a bug, please consider sending a PR with a fix. |
@facebook-github-bot close |
@charpeni tells me to close this issue. If you think it should still be opened let us know why. |
A/libc: Fatal signal 6 (SIGABRT), code -6 in tid 31476 (alhost:8097/...) Facing the same issue react- 16.0.0 |
Do the checklist before filing an issue:
Based on the stack trace, it looks like the issue could be related to JSCExecutor::callFunction() attempting to dereference a null pointer:
https://github.com/facebook/react-native/blob/master/ReactCommon/cxxreact/JSCExecutor.cpp L.365
None of the above, create a bug report
08-18 20:47:58.042 13586-14316/com.samsara.driver A/libc: Fatal signal 6 (SIGABRT), code -6 in tid 14316 (mqt_js)
08-18 20:47:58.152 288-288/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
08-18 20:47:58.152 288-288/? A/DEBUG: Build fingerprint: 'samsung/gt58wifixx/gt58wifi:6.0.1/MMB29M/T350XXU1BPE3:user/release-keys'
08-18 20:47:58.152 288-288/? A/DEBUG: Revision: '4'
08-18 20:47:58.152 288-288/? A/DEBUG: ABI: 'arm'
08-18 20:47:58.152 288-288/? A/DEBUG: pid: 13586, tid: 14316, name: mqt_js >>> com.samsara.driver <<<
08-18 20:47:58.152 288-288/? A/DEBUG: signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
08-18 20:47:58.202 288-288/? A/DEBUG: r0 00000000 r1 000037ec r2 00000006 r3 9d2eb978
08-18 20:47:58.202 288-288/? A/DEBUG: r4 9d2eb980 r5 9d2eb930 r6 00000000 r7 0000010c
08-18 20:47:58.202 288-288/? A/DEBUG: r8 00000004 r9 b8aca670 sl 71c26558 fp 00000000
08-18 20:47:58.202 288-288/? A/DEBUG: ip 00000006 sp 9d2eb340 lr b6d02efd pc b6d052f8 cpsr 400e0010
08-18 20:47:58.222 288-288/? A/DEBUG: backtrace:
08-18 20:47:58.222 288-288/? A/DEBUG: #00 pc 000442f8 /system/lib/libc.so (tgkill+12)
08-18 20:47:58.222 288-288/? A/DEBUG: #1 pc 00041ef9 /system/lib/libc.so (pthread_kill+32)
08-18 20:47:58.222 288-288/? A/DEBUG: #2 pc 0001ba13 /system/lib/libc.so (raise+10)
08-18 20:47:58.222 288-288/? A/DEBUG: #3 pc 00018c81 /system/lib/libc.so (__libc_android_abort+34)
08-18 20:47:58.222 288-288/? A/DEBUG: #4 pc 00016840 /system/lib/libc.so (abort+4)
08-18 20:47:58.222 288-288/? A/DEBUG: #5 pc 0004ee41 /data/app/com.samsara.driver-1/lib/arm/libgnustl_shared.so (_ZN9__gnu_cxx27__verbose_terminate_handlerEv+220)
08-18 20:47:58.222 288-288/? A/DEBUG: #6 pc 0004d93b /data/app/com.samsara.driver-1/lib/arm/libgnustl_shared.so (_ZN10__cxxabiv111__terminateEPFvvE+2)
08-18 20:47:58.222 288-288/? A/DEBUG: #7 pc 0004d96b /data/app/com.samsara.driver-1/lib/arm/libgnustl_shared.so (_ZSt9terminatev+10)
08-18 20:47:58.222 288-288/? A/DEBUG: #8 pc 0004d977 /data/app/com.samsara.driver-1/lib/arm/libgnustl_shared.so (_ZN10__cxxabiv112__unexpectedEPFvvE+2)
08-18 20:47:58.222 288-288/? A/DEBUG: #9 pc 0004cd7d /data/app/com.samsara.driver-1/lib/arm/libgnustl_shared.so (__cxa_call_unexpected+96)
08-18 20:47:58.222 288-288/? A/DEBUG: #10 pc 0002a40d /data/app/com.samsara.driver-1/lib/arm/libreactnativejnifb.so (_ZN8facebook5react11JSCExecutor12callFunctionERKSsS3_RKN5folly7dynamicE+252)
08-18 20:47:58.222 288-288/? A/DEBUG: #11 pc 0002e1b7 /data/app/com.samsara.driver-1/lib/arm/libreactnativejnifb.so
08-18 20:47:58.222 288-288/? A/DEBUG: #12 pc 0002fdf /data/app/com.samsara.driver-1/lib/arm/libreactnativejnifb.so
08-18 20:47:58.222 288-288/? A/DEBUG: #13 pc 00018fb9 /data/app/com.samsara.driver-1/lib/arm/libreactnativejnifb.so (_ZNKSt8functionIFvvEEclEv+12)
08-18 20:47:58.222 288-288/? A/DEBUG: #14 pc 00019b15 /data/app/com.samsara.driver-1/lib/arm/libreactnativejnifb.so
08-18 20:47:58.222 288-288/? A/DEBUG: #15 pc 000142ed /data/app/com.samsara.driver-1/lib/arm/libreactnativejnifb.so
08-18 20:47:58.222 288-288/? A/DEBUG: #16 pc 0015f61f /data/data/com.samsara.driver/cache/slice-com.facebook.react-react-native-0.31.0_79dae5f40368700e06771efc0710b48a928a4c08-classes.dex (offset 0x10f000) (void com.facebook.react.bridge.queue.NativeRunnable.run()+74)
08-18 20:47:58.222 288-288/? A/DEBUG: #17 pc 037a11df /system/framework/arm/boot.oat (offset 0x2f81000)
react-native 0.31
Crash only occurs on Android. This is not 100% reproducible either, seems to intermittently crash in development on app launch.
Mac
The text was updated successfully, but these errors were encountered: