-
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
SIGSEGV 0x0000000000000040 Crash report by Firebase on Samsung devices on Android 12 mostly #33896
Comments
I have exactly the same problem, app crashes on android 12 samsung with same stacktrace. #00 pc 0x6703bc libjsc.so System: *Sorry couldn't make formatting any better. |
@Shevchenko-Oleksii it also can be Samsung issue. |
There are no traces of React Native in the Stacktrace. |
My stacktrace starts with libjsc, so i assumed that's RN related. |
@Shevchenko-Oleksii |
|
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:
|
Hi, @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
|
Reproduced at samsung remotetestlab with jsc-android version 250230.2.1
and with jsc-android@next (294992.0.0)
|
Same issue here. Some info:
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:
Sentry:
|
Same issue: "react-native": "0.67.1" Crashalytics: Application: xxx.xxxxx.xxxxxxxxPlatform: androidVersion: 1.0 (16)Issue: 6528c057dff5cd29ff739044cca8b3c1Session: 639323df011000017c063c4e61274bfb_DNE_0_v2Date: Fri Dec 09 2022 17:32:45 GMT+0530 (India Standard Time)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. |
Yup let's close this then 👍 |
@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:
and
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:
|
@paryanihitesh @karenraianybp |
@arsensgitacc Yes we have enabled that, still seeing this issue |
@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 = [ Crashed: Thread #1 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 |
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 |
Any solution to this Crash we have same problem too. Crashes in android Crash log : any solutions are appreciated |
Naveen562117 |
Crashed: Thread: SIGSEGV 0x0000000000000000 Device Operating System |
Crash report by Firebase on Samsung devices Error:
|
We also get these kinds of crashes and we have been working on fixing these for a few months now
Hope this helps |
Alright! This issue needs to be reopened. |
@paryanihitesh and everyone |
why this issue is closed? |
Any reason to why this issue was closed ?, cause no specific fix. |
+1 |
3 similar comments
+1 |
+1 |
+1 |
+1. Anybody getting this issue with Expo SDK 50+? |
+1 |
still exist |
+1 |
still getting error on RN v 0.74.3 |
i am getting same error on android 11 oneplus 8 pro devices. |
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
The text was updated successfully, but these errors were encountered: