Getting SIGABRT Crash on release build. libc.so
See original GitHub issuePlease provide all the information requested. Issues that do not follow this format are likely to stall.
Description
Did looked for related issues did not find any solution for this, the crash is prominent for almost most of the user on my end on my device im unable to reproduce it if someone has faced the crash please help me get away with this. I have hermes enabled for my app.
React Native version:
System:
OS: Linux 5.8 Manjaro Linux
CPU: (8) x64 Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz
Memory: 14.79 GB / 19.40 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 12.18.3 - ~/.nvm/versions/node/v12.18.3/bin/node
Yarn: Not Found
npm: 6.14.6 - ~/.nvm/versions/node/v12.18.3/bin/npm
Watchman: Not Found
SDKs:
Android SDK: Not Found
IDEs:
Android Studio: Not Found
Languages:
Java: 11.0.8 - /usr/lib/jvm/default/bin/javac
Python: 3.8.5 - /usr/bin/python
npmPackages:
@react-native-community/cli: ^3.0.5-alpha.1 => 3.2.1
react: 16.13.1 => 16.13.1
react-native: 0.63.2 => 0.63.2
npmGlobalPackages:
*react-native*: Not Found
Steps To Reproduce
Unable to produce on my devices but i am able to see this crash on users in production. Probably happening happening while the app starts as i can see in the logs,
Expected Results
This crash is too prominent more than 20% users are facing the crash need a fix
Snack, code example, screenshot, or link to a repository:
Crashed: Thread : SIGABRT 0x000027b900000bf9
#00 pc 0x72c8ba5b3c libc.so
#01 pc 0x72c8ba5b0c libc.so
#02 pc 0x722553f124 libc++_shared.so
#03 pc 0x722553b3d4 libc++_shared.so
#04 pc 0x7224ec43b4 libhermes-executor-release.so
#05 pc 0x7224ec48bc libhermes-executor-release.so
#06 pc 0x7224ebcffc libhermes-executor-release.so
#07 pc 0x7224eae4e8 libhermes-executor-release.so
#08 pc 0x7224eb0c74 libhermes-executor-release.so
#09 pc 0x7224ea84c8 libhermes-executor-release.so
#10 pc 0x7224876264 libhermes.so
#11 pc 0x7224875be4 libhermes.so
#12 pc 0x722487ffac libhermes.so
#13 pc 0x722488e9f0 libhermes.so
#14 pc 0x7224891e34 libhermes.so
#15 pc 0x722488f93c libhermes.so
#16 pc 0x722487fb0c libhermes.so
#17 pc 0x722488ea08 libhermes.so
#18 pc 0x7224891e34 libhermes.so
#19 pc 0x722488f93c libhermes.so
#20 pc 0x722487fb0c libhermes.so
#21 pc 0x722488ea08 libhermes.so
#22 pc 0x7224891e34 libhermes.so
#23 pc 0x722488f93c libhermes.so
#24 pc 0x722487fb0c libhermes.so
#25 pc 0x722488ea08 libhermes.so
#26 pc 0x7224891e34 libhermes.so
#27 pc 0x722488f93c libhermes.so
#28 pc 0x7224900dc0 libhermes.so
#29 pc 0x722487ffac libhermes.so
#30 pc 0x722488e9f0 libhermes.so
#31 pc 0x7224891e34 libhermes.so
#32 pc 0x722488f93c libhermes.so
#33 pc 0x7224900dc0 libhermes.so
#34 pc 0x722487ffac libhermes.so
#35 pc 0x722488e9f0 libhermes.so
#36 pc 0x7224891e34 libhermes.so
#37 pc 0x722488f93c libhermes.so
#38 pc 0x722487ee28 libhermes.so
#39 pc 0x7224900b70 libhermes.so
#40 pc 0x722487ffac libhermes.so
#41 pc 0x722488e9f0 libhermes.so
#42 pc 0x7224891e34 libhermes.so
#43 pc 0x722488f93c libhermes.so
#44 pc 0x722487fb0c libhermes.so
#45 pc 0x722488ea08 libhermes.so
#46 pc 0x7224891e34 libhermes.so
#47 pc 0x722488f93c libhermes.so
#48 pc 0x722487fb0c libhermes.so
#49 pc 0x7224870108 libhermes.so
#50 pc 0x7224eb1334 libhermes-executor-release.so
#51 pc 0x7224eb1190 libhermes-executor-release.so
#52 pc 0x7224eab5e4 libhermes-executor-release.so
#53 pc 0x7224eae034 libhermes-executor-release.so
#54 pc 0x7224fa0d58 libreactnativejni.so
#55 pc 0x7224fa2350 libreactnativejni.so
#56 pc 0x7224f68d48 libreactnativejni.so
#57 pc 0x7224f59a70 libreactnativejni.so
#58 pc 0x7224f599ec libreactnativejni.so
#59 pc 0x724331e9e0 libart.so
#60 pc 0x3ffffffc
#61 pc 0x136412ec
#62 pc 0x19d5213c
#63 pc 0x136412ec
Issue Analytics
- State:
- Created 3 years ago
- Reactions:49
- Comments:70 (13 by maintainers)
Top Results From Across the Web
Diagnosing Native Crashes | Android Open Source Project
A call to abort signals the calling thread with SIGABRT, so a frame showing "abort" in libc.so plus SIGABRT are the things to...
Read more >React Native Android libc.so crash on first open after installation
Everything is working fine in debug mode. If I uninstall the app and reinstall from an apk, the first time is crashing.
Read more >app crashes with EXC_CRASH (SIGABR… - Apple Developer
But in my case, it is just kind of unclear how I could proceed from what I can get from the crash log....
Read more >Get useful stack trace when app crash with Signal 6 (SIGABRT)
This stack trace is not useful for me to get back the crash issues from the source code, because all thing point to...
Read more >No backtrace on SIGABRT caused by malloc error
The crash happens when the application is destroying an object that has several sub-objects that are running on their own threads. The error ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Any update? I’ve been encountering this problem since I updated RN version 0.59.10 to 0.63.3
Same issue on
react-native: 0.63.3