Closed arsensgitacc closed 1 year ago
I have exactly the same problem, app crashes on android 12 samsung with same stacktrace. Perhaps related to: https://github.com/facebook/react-native/issues/24261 Seems like changing engine works most of the time, i'll try to use Hermes. Edit: My stacktrace Crashed: Thread : SIGSEGV 0x0000000000000048
System: OS: macOS 12.3.1 CPU: (8) arm64 Apple M1 Memory: 105.53 MB / 8.00 GB Shell: 5.8 - /bin/zsh Binaries: Node: 18.0.0 - /opt/homebrew/bin/node Yarn: 1.22.17 - ~/.yarn/bin/yarn npm: 8.6.0 - /opt/homebrew/bin/npm Watchman: 2022.03.21.00 - /opt/homebrew/bin/watchman Managers: CocoaPods: 1.11.3 - /opt/homebrew/bin/pod SDKs: iOS SDK: Platforms: DriverKit 21.4, iOS 15.4, macOS 12.3, tvOS 15.4, watchOS 8.5 Android SDK: API Levels: 28, 29, 30, 31 Build Tools: 28.0.3, 29.0.2, 29.0.3, 30.0.2, 31.0.0 System Images: android-29 | Intel x86 Atom, android-31 | Google APIs ARM 64 v8a Android NDK: Not Found IDEs: Android Studio: 2021.1 AI-211.7628.21.2111.8139111 Xcode: 13.3/13E113 - /usr/bin/xcodebuild Languages: Java: 1.8.0_292 - /usr/bin/javac npmPackages: @react-native-community/cli: Not Found react: 17.0.2 => 17.0.2 react-native: 0.66.4 => 0.66.4 react-native-macos: Not Found npmGlobalPackages: react-native: Not Found
*Sorry couldn't make formatting any better.
@Shevchenko-Oleksii it also can be Samsung issue. https://eu.community.samsung.com/t5/galaxy-s20-series/apps-crashing-after-android-12-update/td-p/4672799
Crashed: Thread : SIGSEGV 0x0000000000000040
#00 pc 0x78ffc5cbbc
#01 pc 0x664 linux-vdso.so.1
#02 pc 0x17ea8 libutils.so
#03 pc 0x17d84 libutils.so
#04 pc 0x159140 libandroid_runtime.so
...
#10 pc 0xa16ffc libart.so
...
#13 pc 0x26934 libc.so
...
#16 pc 0xa14ffc libart.so
...
#60 pc 0x407c app_process64
There are no traces of React Native in the Stacktrace. Are you able to consistently reproduce this in any form?
Crashed: Thread : SIGSEGV 0x0000000000000040
#00 pc 0x78ffc5cbbc
#01 pc 0x664 linux-vdso.so.1
#02 pc 0x17ea8 libutils.so
#03 pc 0x17d84 libutils.so
#04 pc 0x159140 libandroid_runtime.so
...
#10 pc 0xa16ffc libart.so
...
#13 pc 0x26934 libc.so
...
#16 pc 0xa14ffc libart.so
...
#60 pc 0x407c app_process64
There are no traces of React Native in the Stacktrace. Are you able to consistently reproduce this in any form?
My stacktrace starts with libjsc, so i assumed that's RN related. I was able to constantly reproduce in our app, i'll try with mre on clean project later, or let me know if I can help debugging this.
@Shevchenko-Oleksii How were you reproducing it? Can you please describe steps?
:warning: | Missing Reproducible Example |
---|---|
:information_source: | It looks like your issue is missing a reproducible example. Please provide a Snack or a repository that demonstrates the issue you are reporting in a minimal, complete, and reproducible manner. |
if someone can repro the crash in house and could help to verify whether the updated jsc fixing the crash, that would be appreciated.
upgrade steps:
yarn add jsc-android@next
android/app/build.gradle
and change 'org.webkit:android-jsc:+'
to 'org.webkit:android-jsc-intl:+'
Hi, Our application has encountered this issue since we upgraded to 0.69. Activate hermes have fixed the problem for us.
@Kudo : For curiosity, I tried to test your solution (add jsc-android@next with disable hermes), but I couldn't compile with it (seems to be a conflict with Reanimated). I didn't tried to fix this issue.
Edit : In fact, it was not exactly the same crash, it was a crash on libjsc.so on the first launch post installation on some samsung in android 12.
Envoyé de mon iPhone
Le 7 sept. 2022 à 14:20, GaelCO @.***> a écrit :
Hi, Our application has encountered this issue since we upgraded to 0.69. Activate hermes have fixed the problem for us.
@Kudo : For curiosity, I tried to test your solution (add @.*** with disable hermes), but I couldn't compile with it (seems to be a conflict with Reanimated). I didn't tried to fix this issue.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.
have a similar crash on Galaxy S20 5G/Note10 Lite/A22 5G/Galaxy A53 5G/Galaxy S10+/Galaxy S22/Galaxy A52s 5G/Galaxy S21 Ultra 5G/Galaxy S21 Ultra 5G/Pretty much all samsungs, android 12 and react 0.63.4
Crashed: Thread : SIGSEGV 0x0000000000000040
#00 pc 0x646bbc libjsc.so
#01 pc 0x71ef7c85cc
#02 pc 0xf540 libart.so
#03 pc 0xf540 libart.so
Reproduced at samsung remotetestlab with jsc-android version 250230.2.1
Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x48 in tid 24761 (xxxx), pid 24761 (xxxx)
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/y2seea/y2s:12/SP1A.210812.016/G985FXXSEFVE6:user/release-keys'
Revision: '22'
ABI: 'arm64'
Processor: '5'
Timestamp: 2022-10-25 12:51:25.234091061+0200
Process uptime: 8s
Cmdline: xxxx
pid: 24761, tid: 24761, name: xxxx >>> xxxx <<<
uid: 10556
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x48
Cause: null pointer dereference
x0 000000000000000a x1 0000007fdfbac8d0 x2 0000007fdfbac950 x3 000000000000053d
x4 0000000000000000 x5 0000000000000008 x6 000000006f9ce2b8 x7 00000000001f331c
x8 0000007724fd1c10 x9 0000000000000000 x10 000000787d212000 x11 00000000000000e0
x12 0000000000000008 x13 0000000092451018 x14 000e4e0f051b9980 x15 0000377c06c441dc
x16 0000007aef539d40 x17 0000007aed929520 x18 0000007af2784000 x19 000000788d228190
x20 0000000000000000 x21 000000000000053d x22 000000000000053d x23 000000788d228190
x24 0000000070b55d70 x25 0000007af244e000 x26 000000006f9ce2b8 x27 0000000013056330
x28 000000781d278360 x29 0000007fdfbadb20
lr 0000007af361e678 sp 0000007fdfbac8b0 pc 0000007724da63bc pst 0000000060000000
backtrace:
#00 pc 00000000006703bc /data/app/xxxxx==/xxxxx==/lib/arm64/libjsc.so (BuildId: dad225e5c5aafb43e3fcbfcd576772a6a0f8c19a)
#01 pc 0000000000000678 [vdso] (__kernel_rt_sigreturn+0)
#02 pc 000000000009fca4 /apex/com.android.runtime/lib64/bionic/libc.so (__epoll_pwait+4) (BuildId: 9f96e1e92e346f8dd579bdcb20b6c618)
#03 pc 000000000001663c /system/lib64/libutils.so (android::Looper::pollInner(int)+180) (BuildId: a8e5883b039c6d018dc9ced53f79b1d0)
#04 pc 0000000000016520 /system/lib64/libutils.so (android::Looper::pollOnce(int, int*, int*, void**)+112) (BuildId: a8e5883b039c6d018dc9ced53f79b1d0)
#05 pc 0000000000152c18 /system/lib64/libandroid_runtime.so (android::android_os_MessageQueue_nativePollOnce(_JNIEnv*, _jobject*, long, int)+44) (BuildId: 6d19114713bb65d163a18308398a7105)
#06 pc 00000000003fe504 /data/misc/apexdata/com.android.art/dalvik-cache/arm64/boot.oat (art_jni_trampoline+116)`
#00 pc 00000000006703bc /data/app/xxxxx==/xxxxx==/lib/arm64/libjsc.so (BuildId: dad225e5c5aafb43e3fcbfcd576772a6a0f8c19a)
#01 pc 0000000000000678 [vdso] (__kernel_rt_sigreturn+0)
#02 pc 000000000009fca4 /apex/com.android.runtime/lib64/bionic/libc.so (__epoll_pwait+4) (BuildId: 9f96e1e92e346f8dd579bdcb20b6c618)
#03 pc 000000000001663c /system/lib64/libutils.so (android::Looper::pollInner(int)+180) (BuildId: a8e5883b039c6d018dc9ced53f79b1d0)
#04 pc 0000000000016520 /system/lib64/libutils.so (android::Looper::pollOnce(int, int*, int*, void**)+112) (BuildId: a8e5883b039c6d018dc9ced53f79b1d0)
#05 pc 0000000000152c18 /system/lib64/libandroid_runtime.so (android::android_os_MessageQueue_nativePollOnce(_JNIEnv*, _jobject*, long, int)+44) (BuildId: 6d19114713bb65d163a18308398a7105)
#06 pc 00000000003fe504 /data/misc/apexdata/com.android.art/dalvik-cache/arm64/boot.oat (art_jni_trampoline+116)
and with jsc-android@next (294992.0.0)
Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x40 in tid 26691 (xxxxx), pid 26691 (xxxxx)
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/t2sxxx/t2s:12/SP1A.210812.016/G996BXXU5CVGB:user/release-keys'
Revision: '22'
ABI: 'arm64'
Processor: '5'
Timestamp: 2022-10-25 13:28:31.772828625+0200
Process uptime: 8s
Cmdline: xxxxx
pid: 26691, tid: 26691, name: xxxxx >>> xxxxx <<<
uid: 10543
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x40
Cause: null pointer dereference
x0 000000000000000a x1 0000007fd95e1670 x2 0000007fd95e16f0 x3 0000000000000936
x4 0000000000000000 x5 0000000000000008 x6 000000006fcaa2b8 x7 000000006fcaa410
x8 0000006c4394ec50 x9 0000000000000000 x10 0000006d730f3000 x11 00000000000000e0
x12 0000000000000018 x13 000000004930faac x14 00032a9cb5544980 x15 0000000026762762
x16 0000006fcf3edd40 x17 0000006fd73bb520 x18 0000006ff32f4000 x19 b400006d8310b850
x20 0000000000000000 x21 0000000000000936 x22 0000000000000936 x23 b400006d8310b850
x24 0000000070e32e88 x25 0000006ff2e5c000 x26 000000006fcaa2b8 x27 0000000012c27470
x28 b400006d1312cfd0 x29 0000007fd95e28c0
lr 0000006ff402f5d0 sp 0000007fd95e1650 pc 0000006c4381c510 pst 0000000060001000
backtrace:
#00 pc 00000000011db510 /data/app/~~WSmJpZdbW4ZdSl9XDicSsA==/xxxxx-FFHDFGgNrKv6mGMlj83m2A==/lib/arm64/libjsc.so (BuildId: 93cb2557fdecd7c4b61b12cc256864763ab0df6a)
#01 pc 00000000000005d0 [vdso] (__kernel_rt_sigreturn+0)
#02 pc 000000000009fca4 /apex/com.android.runtime/lib64/bionic/libc.so (__epoll_pwait+4) (BuildId: 1001969d8caf747bff324cbb95af4b2e)
#03 pc 000000000001663c /system/lib64/libutils.so (android::Looper::pollInner(int)+180) (BuildId: a8e5883b039c6d018dc9ced53f79b1d0)
#04 pc 0000000000016520 /system/lib64/libutils.so (android::Looper::pollOnce(int, int*, int*, void**)+112) (BuildId: a8e5883b039c6d018dc9ced53f79b1d0)
#05 pc 0000000000152c20 /system/lib64/libandroid_runtime.so (android::android_os_MessageQueue_nativePollOnce(_JNIEnv*, _jobject*, long, int)+44) (BuildId: 39cec9e5522801005770df24c636b665)
#06 pc 00000000003fe504 /data/misc/apexdata/com.android.art/dalvik-cache/arm64/boot.oat (art_jni_trampoline+116)
Same issue here. Some info:
99% Samsung
Will try to upgrade React Native soon, but note that even the latest version of RN includes this version of jsc-android. Will also try to use jsc-android@next as soon as I can reproduce this issue.
Crashlytics:
Crashed: Thread: SIGSEGV 0x0000000000000048
#00 pc 0x857fb4 libjsc.so
#01 pc 0x898 linux-vdso.so.1
#02 pc 0x17444 libutils.so
#03 pc 0x17328 libutils.so
#04 pc 0x16117c libandroid_runtime.so
#05 pc 0x58cb60 boot-framework.oat
#06 pc 0x589e68 boot-framework.oat
#07 pc 0x589d60 boot-framework.oat
#08 pc 0x2ee384 boot-framework.oat
#09 pc 0xa15ffc libart.so
#10 pc 0x434600 libart.so
#11 pc 0x466d34 libart.so
#12 pc 0x1c3bb0 boot-framework.oat
#13 pc 0x508d74 boot-framework.oat
#14 pc 0x50aacc boot-framework.oat
#15 pc 0x466564 libart.so
#16 pc 0x99148 boot.oat
#17 pc 0x503f30 boot-framework.oat
#18 pc 0x50d24c boot-framework.oat
#19 pc 0xd64f0 libart.so
#20 pc 0x434600 libart.so
#21 pc 0x57e378 libart.so
#22 pc 0x5f1d7c libart.so
#23 pc 0x228ffc libandroid_runtime.so
#24 pc 0x464eb8 libart.so
#25 pc 0xbfad0 libandroid_runtime.so
#26 pc 0x22957c libandroid_runtime.so
#27 pc 0x72e4 libnativehelper.so
#28 pc 0x7e70f libandroid_runtime.so
#29 pc 0xcbdf8 libandroid_runtime.so
#30 pc 0x136f app_process64
#31 pc 0xb9518 libc.so
#32 pc 0x1347fc ld-android.so
#33 pc 0x139f app_process64
#34 pc 0xb9518 libc.so
#35 pc 0x1347fc ld-android.so
#36 pc 0x1488c libutils.so
#37 pc 0xc7f94 libandroid_runtime.so
#38 pc 0x139f app_process64
#39 pc 0x2568 app_process64
#40 pc 0x139f app_process64
#41 pc 0x307c app_process64
#42 pc 0x307c app_process64
#43 pc 0x303c app_process64
#44 pc 0x20c1b4 libandroid_runtime.so
#45 pc 0x307c app_process64
Sentry:
Exception Type: Unknown (SIGSEGV)
Application Specific Information:
Segfault
Thread 0 Crashed:
0 libjsc.so 0x73edae7fb4 <unknown> + 497908875188
1 [vdso] 0x752fc75628 __kernel_rt_sigreturn
2 libc.so 0x752bd81184 <unknown> + 503246754180
3 libutils.so 0x751942c524 _ZN7android6Looper9pollInnerEi
4 libutils.so 0x751942c408 _ZN7android6Looper8pollOnceEiPiS1_PPv
5 libandroid_runtime.so 0x75247c5d98 <unknown> + 503123303832
6 boot.oat 0x7180d504 <unknown> + 1904268548
EOF
Same issue:
"react-native": "0.67.1" I already @Kudo solution but it's not work for me https://github.com/facebook/react-native/issues/33896#issuecomment-1183355650
Crashalytics: `# Crashlytics - Stack trace
Crashed: Thread: SIGSEGV 0x0000000000000048
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
Thread:
@ahtokca @martijnhoutman @cortinico @StanSarr Anyone has a solution please share its will great help.
Well, I am still in the process of fixing the issue. It is still impossible for me to reproduce this issue, but there are still about 1% crashes for our Android users according to Crashlytics and Sentry.
But I did make progress which seems to have fixed this issue for a new release: I have updated to React Native 0.68.5, and enabled Hermes for Android. The crash does not re-appear up until now, but so far the rollout on Android is only done for the first 5% of the users, so it is still too early to tell for sure.
Hi @martijnhoutman - was this resolved for you in the end?
@Nick-Patrick Yes, we have not yet seen this specific issue pop up since our upgrade to Hermes, and we have reached a >90% rollout by now.
@Nick-Patrick, @codal-mpawar We have upgraded react native 0.64.4=>0.70.6. That was not the easiest thing to do, but the crash is gone. So should I close this issue?
That was not the easiest thing to do, but the crash is gone. So should I close this issue?
Yup let's close this then 👍
I can see the issue is closed but I'm still having the crash on Android 13. I enabled Hermes but nothing worked. It seems the crash is mostly on Samsung devices. Any workaround without upgrading the RN version? I'm currently on RN v0.67.5
@Nick-Patrick @codal-mpawar any advice?
I upgraded to RN 0.70.6 and started seeing this crash. I upgraded to 0.71.3, and it persisted. If I enable hermes, it (obviously) goes away. I'd like to not switch the runtime to fix a single crash. Here's the full stack trace I get.
adb logcat | ~/Android/sdk/ndk/23.1.7779620/ndk-stack -sym jni/arm64-v8a/libjsc.so
********** Crash dump: **********
Build fingerprint: 'samsung/z3quew/z3q:12/SP1A.210812.016/G988U1UES3FVK1:user/release-keys'
#00 0x00000000005032e4 /data/app/~~VtVNBRifuJ04N56RIsWoRQ==/my.app.bundle.id--LnOREf5niSbPh06Kw3gXw==/base.apk!libjsc.so (BuildId: 9cb83e4124e3ee1471bc717c722b4109614385ba)
#01 0x0000000000000678 [vdso] (__kernel_rt_sigreturn+0)
#02 0x00000000000a30b8 /apex/com.android.runtime/lib64/bionic/libc.so (__epoll_pwait+8) (BuildId: b5d187ac75fe4580e13ab2ec624bf7f1)
#03 0x0000000000017ea8 /system/lib64/libutils.so (android::Looper::pollInner(int)+184) (BuildId: 748948a5650ad93d18b12eb1d9a51a89)
#04 0x0000000000017d84 /system/lib64/libutils.so (android::Looper::pollOnce(int, int*, int*, void**)+116) (BuildId: 748948a5650ad93d18b12eb1d9a51a89)
#05 0x0000000000159170 /system/lib64/libandroid_runtime.so (android::android_os_MessageQueue_nativePollOnce(_JNIEnv*, _jobject*, long, int)+48) (BuildId: 33b6cccb8cb818db0b8648d93b8de614)
#06 0x00000000003fe504 /data/misc/apexdata/com.android.art/dalvik-cache/arm64/boot.oat (art_jni_trampoline+116)
Crash dump is completed
Facing same error on on crashlytics logs: SIGSEGV 0x0000000000000010
React Native : 0.64.4
I'll update after verifying it on the latest version. Meanwhile, if someone has verified the same issue or has another workaround, any help would be appreciated.
No, Still we are getting random errors. @mitchiemt11 @arsensgitacc
Guys, I have version 0.70.8 and the error still happens.
That's sad to hear. We did not yet run into this issue since the last upgrade to 0.68. We are in the process of upgrading to 0.71, if any regression happens, I will be sure to update that here.
@martijnhoutman We are on version 0.71 and are still seeing this crash, any update on your side?
We have only been running the 71 version of the app in alpha and beta release (i.e. a select group of people), but so far no more crashes.
The only references I can find in our gradle file to JSC are these:
/**
* The preferred build flavor of JavaScriptCore (JSC)
*
* For example, to use the international variant, you can use:
* `def jscFlavor = 'org.webkit:android-jsc-intl:+'`
*
* The international variant includes ICU i18n library and necessary data
* allowing to use e.g. `Date.toLocaleString` and `String.localeCompare` that
* give correct results when using with locales other than en-US. Note that
* this variant is about 6MiB larger per architecture than default.
*/
def jscFlavor = 'org.webkit:android-jsc-intl:+'
and
if (hermesEnabled.toBoolean()) {
implementation("com.facebook.react:hermes-android")
} else {
implementation jscFlavor
}
I think these are just the default values, not entirely sure about the jsc-intl. Maybe this helps?
Edit: come to think of it, should Hermes not fully replace JSC? can you confirm you are running Hermes? E.g. by rendering a component on some view like this:
<Text>(Hermes enabled: {global.HermesInternal ? "Yes" : "No"})</Text>
@paryanihitesh @karenraianybp Do you have 'hermesEnabled=true' in your gradle.properties?
@arsensgitacc Yes we have enabled that, still seeing this issue Do you mind sharing your android/build.gradle and android/app/build.gradle?
@paryanihitesh Unfortunately, I can no longer access the project with that solved issue.
@martijnhoutman Yes I verified, hermes is enabled in the project
We have upgraded react native from 0.67.4 to 0.69.9 with hermes enabled. project.ext.react = [
enableHermes: true,
]. We are seeing lot of crashes on xiaomi and samsung devices like this
Crashed: Thread #1 SIGSEGV 0x0000000087aa6000 0 libc.so (Missing BuildId a023aa67e77f963c063f5ddccc9af208) app_issue_f4e23ef0af3b92e13a709b01f249ecfd_crash_session_646f2d85010f00010a1509de538becb6_DNE_0_v2_stacktrace.txt
Can anyone please provide solution for this?
I'm seeing this issue as well
Was anyone able to solve this?
Also getting the same issue
We have upgraded react native from 0.67.4 to 0.69.9 with hermes enabled. project.ext.react = [ enableHermes: true, ]. We are seeing lot of crashes on xiaomi and samsung devices like this
Crashed: Thread #1 SIGSEGV 0x0000000087aa6000 0 libc.so (Missing BuildId a023aa67e77f963c063f5ddccc9af208) app_issue_f4e23ef0af3b92e13a709b01f249ecfd_crash_session_646f2d85010f00010a1509de538becb6_DNE_0_v2_stacktrace.txt
Can anyone please provide solution for this?
I have the same bug as you. Have you resolved it?
we are also getting this kind of issue with the updation of reanimated library. RN 0.67.5 and Hermes is off Crashed: null pointer dereference #1 SIGSEGV 0x000000000000000a 0 libjsc.so (Missing BuildId dad225e5c5aafb43e3fcbfcd576772a6a0f8c19a)
Any solution to this Crash we have same problem too. we Upgraded the React native 0.68.2 to 0.71.7
Crashes in android
Crash log : Crashed: Thread: SIGSEGV 0x000000000000002c
any solutions are appreciated
Naveen562117 im using reanimated with 2.17.0 and gesture handler 2.9.0 for RN 0.67.5 for RN 0.72.3 reanimated 3.4.1 and gesture handler 2.9.0
Crashed: Thread: SIGSEGV 0x0000000000000000
Device Brand:Samsung Model:Galaxy S21 5G Orientation:Unknown RAM free: 253.5 MB Disk free: 53.71 GB
Operating System Version:Android 13 Orientation:Unknown Rooted:No
Crash report by Firebase on Samsung devices
Error:
null pointer dereference: SIGSEGV 0x0000000000000048
#00 pc 0x6703bc libjsc.so (BuildId: dad225e5c5aafb43e3fcbfcd576772a6a0f8c19a)
#01 pc 0x5bc linux-vdso.so.1 (BuildId: 8d7aa7f9971b098c)
#02 pc 0x17ffc libutils.so (BuildId: 62128a51f31d41bbd0d14333ccf95e95)
#03 pc 0x17ee0 libutils.so (BuildId: 62128a51f31d41bbd0d14333ccf95e95)
#04 pc 0x1659fc libandroid_runtime.so (BuildId: 060586aba45c146d9d07ddfe425525ba)
#05 pc 0x72d2e1a8
#06 pc 0x72d2a3d8
#07 pc 0x72d2a1ec
#08 pc 0x72a072c4
#09 pc 0x458000 libart.so (BuildId: 4bf4747707ca903605931dd6b3d0480c)
#10 pc 0x48ad9c libart.so (BuildId: 4bf4747707ca903605931dd6b3d0480c)
#11 pc 0x72473854
"react": "18.0.0",
"react-native": "0.69.12",
We also get these kinds of crashes and we have been working on fixing these for a few months now Sharing what we have learnt so far
Hope this helps
We also get these kinds of crashes and we have been working on fixing these for a few months now Sharing what we have learnt so far
- Every SIGSEGV has a different root cause and needs to be dealt with differently
- One particular variant of SIGSEGV was directly proportional to the number of ANRs we were getting. So we fixed ANRs and were able to decrease these crashes
- Some native libraries might be using a different version than what react-native is using. You can also check for that
Hope this helps
Alright! This issue needs to be reopened.
@paryanihitesh and everyone When I was looking into the possible reason for the crash, I found that sometimes I am getting logs of events for googleSignIn. Do you have similar observations?
why this issue is closed?
Any reason to why this issue was closed ?, cause no specific fix.
+1
+1
+1
+1.
Anybody getting this issue with Expo SDK 50+?
Description
Firebase crash report
Crashed: Thread : SIGSEGV 0x0000000000000040
#00 pc 0x78ffc5cbbc
#01 pc 0x664 linux-vdso.so.1
#02 pc 0x17ea8 libutils.so
#03 pc 0x17d84 libutils.so
#04 pc 0x159140 libandroid_runtime.so
...
#10 pc 0xa16ffc libart.so
...
#13 pc 0x26934 libc.so
...
#16 pc 0xa14ffc libart.so
...
#60 pc 0x407c app_process64
Devices
84% - samsung 8% - motorola 3% - TCL 3% - Google
Android versions
84% - Android 12 8% - Android 11 3% - Android 7 3% - Android 9
Crash cannot be reproduced It happens mostly once per user mostly with free ram < 300MB
Version
0.64.3
Output of
npx react-native info
System: OS: macOS 12.3.1 CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz Memory: 62.82 MB / 16.00 GB Shell: 5.8 - /bin/zsh Binaries: Node: 18.0.0 - /usr/local/bin/node Yarn: 1.22.17 - /usr/local/bin/yarn npm: 8.6.0 - /usr/local/bin/npm Watchman: 2022.03.21.00 - /usr/local/bin/watchman Managers: CocoaPods: 1.11.3 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3 Android SDK: API Levels: 30, 31, 32 Build Tools: 30.0.2, 32.0.0 System Images: android-29 | Google Play Intel x86 Atom, android-31 | Google APIs Intel x86 Atom_64 Android NDK: Not Found IDEs: Android Studio: 2020.3 AI-203.7717.56.2031.7935034 Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild Languages: Java: 11.0.2 - /usr/bin/javac npmPackages: @react-native-community/cli: Not Found react: 17.0.1 => 17.0.1 react-native: 0.64.3 => 0.64.3 react-native-macos: Not Found npmGlobalPackages: react-native: Not Found
Steps to reproduce
Crash cannot be reproduced even on devices that firebase shows
Snack, code example, screenshot, or link to a repository
Not available