libc.so crash in production build

[infapednekar]

Description

Getting libc.so crashes in firebase Crashlytics dashboard. The majority of these devices are Samsung devices.

React Native version:

System:
OS: macOS 10.15.7
CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Memory: 57.18 MB / 16.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 14.8.0 - /usr/local/bin/node
Yarn: 1.22.4 - /usr/local/bin/yarn
npm: 6.14.7 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.9.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
Android SDK:
API Levels: 23, 24, 27, 28, 29, 30
Build Tools: 28.0.3, 29.0.2, 29.0.3, 30.0.1
System Images: android-26 | Google Play Intel x86 Atom, android-28 | Google Play Intel x86 Atom, android-30 | Google APIs Intel x86 Atom
Android NDK: Not Found
IDEs:
Android Studio: 4.0.1 4.0.1
Xcode: 12.4/12D4e - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_262 - /usr/bin/javac
Python: 2.7.16 - /usr/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.1 => 17.0.1
react-native: 0.63.3 => 0.63.3
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found

Steps To Reproduce

Unable to reproduce the crash. We can see it happening in production build based on crashlytics.

Expected Results

The app should not crash.

Snack, code example, screenshot, or link to a repository:

Crashed: Thread : SIGSEGV 0x0000007e297bd378
#00 pc 0x7e355bfaf4 libjsc.so
#1 pc 0x7e297b1988
#2 pc 0x7e29790d4c
#3 pc 0x7e296ebeb0
#4 pc 0x7e29786724
#5 pc 0x7e296e6784
#6 pc 0x7e297aa46c
#7 pc 0x7e3560acd0 libjsc.so
#8 pc 0x7e3560acd0 libjsc.so
#9 pc 0x7e355f66f4 libjsc.so
#10 pc 0x7e35547778 libjsc.so
#11 pc 0x7e3560ad70 libjsc.so
#12 pc 0x7e3560ad70 libjsc.so
#13 pc 0x7e3560acd0 libjsc.so
#14 pc 0x7e3560acd0 libjsc.so
#15 pc 0x7e3560acd0 libjsc.so
#16 pc 0x7e3560ad70 libjsc.so
#17 pc 0x7e3560ad70 libjsc.so
#18 pc 0x7e3560ad70 libjsc.so
#19 pc 0x7e3560ad70 libjsc.so
#20 pc 0x7e3560ad70 libjsc.so
#21 pc 0x7e29687c64
#22 pc 0x7e29689cd8
#23 pc 0x7e29687c64
#24 pc 0x7e3560acd0 libjsc.so
#25 pc 0x7e3560ad70 libjsc.so
#26 pc 0x7e29736550
#27 pc 0x7e297341e0
#28 pc 0x7e29734e44
#29 pc 0x7e2972a258
#30 pc 0x7e3560acd0 libjsc.so
#31 pc 0x7e3560acd0 libjsc.so
#32 pc 0x7e3560acd0 libjsc.so
#33 pc 0x7e2972aa54
#34 pc 0x7e3560acd0 libjsc.so
#35 pc 0x7e29505838
#36 pc 0x7e355f66f4 libjsc.so
#37 pc 0x7e35547778 libjsc.so
#38 pc 0x7e355477d0 libjsc.so
#39 pc 0x7e352e5128 libjscexecutor.so
#40 pc 0x7e352e4f60 libjscexecutor.so
#41 pc 0x7e35cb8370 libreactnativejni.so
#42 pc 0x7e35cb9350 libreactnativejni.so
#43 pc 0x7e35c7fd48 libreactnativejni.so
#44 pc 0x7e35c70a70 libreactnativejni.so
#45 pc 0x7e35c709ec libreactnativejni.so

[giuthub]

Facebook App (Canhbui. Facebook App)

[riadhriadh]

i think this article can be help you
https://source.android.com/devices/tech/debug/native-crash

[cortinico]

Hey,
We're cleaning up the React Native issue tracker to make sure we focus on the most important issues first.

I'm closing this one because it's stale and related to a version of React Native we no longer support. If the issue persists on the latest version, please re-open a new issue and reference this one.

Moreover, we generally can't fix issues just by looking at a stacktrace reported from your crash reporting platform. Please provide a reproducer in your future reports.

Thank you.