SIGSEGV 0x0000000000000040 Crash report by Firebase on Samsung devices on Android 12 mostly
See original GitHub issueDescription
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® Core™ 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
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:15 (2 by maintainers)
Top GitHub Comments
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:+'
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.