react-native: Getting SIGABRT Crash on release build. libc.so
Please 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
About this issue
- Original URL
- State: open
- Created 4 years ago
- Reactions: 51
- Comments: 94 (14 by maintainers)
Same issue on
react-native: 0.63.3
Any update? I’ve been encountering this problem since I updated RN version 0.59.10 to 0.63.3
Finally I was able to reproduce the crash on one of my test device -
The crash looks something like that at least in my case
/system/lib64/libhwui.so (SkSurface::getCanvas()+16)
was the reason for crash.This comment helped me to resolve this crash - https://github.com/software-mansion/react-native-screens/issues/105#issuecomment-664353593
Basically there is an issue with
react-native-webview
addingandroidHardwareAccelerationDisabled={true}
to your webview should stop this crash. At least the one I’ve mentioned above. I’ve tested it and it did stop the app from crashing.Same issue here, very frustrating.
What i have found out that almost all of the crashes in my case is happening in Redmi/Mi Devices.
We experienced the same crash after upgrade targetSdk from 28 to 29.
We are on RN 0.59.10 and currently have difficulties to upgrade RN version.
Most crashes happened on app start. Our crash stack is:
Crashed: Thread : SIGSEGV 0x0000000000000010 #00 pc 0x75c6647748 libjsc.so #01 pc 0x75c6693fe8 libjsc.so #02 pc 0x76cd285314 libc.so
Anyone know how to solve this? @wangchongwei did you find a solution?
About 5% of my users experience this crash sometimes. And I also could not reproduce it. But recently, when a user contacted our technical support, some employees managed to do it. A crash occurs when uploading several images (more than 4-5) from the device to our server. For loading, we use the image-crop-picker, form the data from it into FormData and send it to the server using axios. For 5-6 photos in a row, the application simply crashes, and this crash comes to crashlytic. Nevertheless, the crash is reproduced not on all devices, but it definitely happens on Xiaomi Mi A2, Samsung Galaxy S20. I still can’t reproduce on my device (redmi note8 pro), but hopefully it helps someone here to reproduce.
react-native: 0.63.4 with Hermes engine.
This bug is happening to some of my users, 100% HUAWEI phones, and android 9-10
Hi. We’ve started to get the same crash in crashlytics after releasing new version with target sdk set to
29
(before it was28
). Effecting mainlyAndroid 10
(80% of all crashes) andAndroid 9
(15% of all crashes) devices. From the logs it seems like a lot of them are happening on the startup. But quite few at random time.We’ve tried to reproduce it on different devices and emulators - no luck.
Hermes is disabled, running
react-native@0.61.5
.Any Update on this getting the same error after integrating React Native into our native android project? Not able to reproduce this every time in production users are facing this, which happened on my device once. Scratching my head for the last week but no clue. Please help 🙏 .
Crashed: Thread: SIGABRT 0x0000000000000000 #00 pc 0x831b0 libc.so (BuildId: 6b76c2818decbeeffb452dac42dbc626) #01 pc 0x83180 libc.so (BuildId: 6b76c2818decbeeffb452dac42dbc626) #02 pc 0x4b988c libart.so (BuildId: d959f7764f0c7e197333334aa9fc1681) #03 pc 0xb458 libbase.so (BuildId: 4ff6e3fcb2702e6b445e1f4b073ca3be) #04 pc 0x3784dc libart.so (BuildId: d959f7764f0c7e197333334aa9fc1681) #05 pc 0x38a03c libart.so (BuildId: d959f7764f0c7e197333334aa9fc1681) #06 pc 0x2681ac libreanimated.so (BuildId: b33f7f3a989aeba7d50079f8a75d97ebc6e5cdb6) #07 pc 0x26428c libreanimated.so (BuildId: b33f7f3a989aeba7d50079f8a75d97ebc6e5cdb6) #08 pc 0x2868c8 libreanimated.so (BuildId: b33f7f3a989aeba7d50079f8a75d97ebc6e5cdb6) #09 pc 0x2b161c libreanimated.so (BuildId: b33f7f3a989aeba7d50079f8a75d97ebc6e5cdb6) #10 pc 0x2b1564 libreanimated.so (BuildId: b33f7f3a989aeba7d50079f8a75d97ebc6e5cdb6) #11 pc 0x2b1478 libreanimated.so (BuildId: b33f7f3a989aeba7d50079f8a75d97ebc6e5cdb6) #12 pc 0x2b13e4 libreanimated.so (BuildId: b33f7f3a989aeba7d50079f8a75d97ebc6e5cdb6) #13 pc 0x2af53c libreanimated.so (BuildId: b33f7f3a989aeba7d50079f8a75d97ebc6e5cdb6) #14 pc 0x1ac920 libreanimated.so (BuildId: b33f7f3a989aeba7d50079f8a75d97ebc6e5cdb6) #15 pc 0x1746a4 libreanimated.so (BuildId: b33f7f3a989aeba7d50079f8a75d97ebc6e5cdb6) #16 pc 0x17460c libreanimated.so (BuildId: b33f7f3a989aeba7d50079f8a75d97ebc6e5cdb6) #17 pc 0x1b25a8 libreanimated.so (BuildId: b33f7f3a989aeba7d50079f8a75d97ebc6e5cdb6) #18 pc 0x2d6aac libreanimated.so (BuildId: b33f7f3a989aeba7d50079f8a75d97ebc6e5cdb6) #19 pc 0x2d69e8 libreanimated.so (BuildId: b33f7f3a989aeba7d50079f8a75d97ebc6e5cdb6) #20 pc 0x2d68d4 libreanimated.so (BuildId: b33f7f3a989aeba7d50079f8a75d97ebc6e5cdb6) #21 pc 0x2d6820 libreanimated.so (BuildId: b33f7f3a989aeba7d50079f8a75d97ebc6e5cdb6) #22 pc 0x2d4994 libreanimated.so (BuildId: b33f7f3a989aeba7d50079f8a75d97ebc6e5cdb6) #23 pc 0x25230 libhermes_executor.so (BuildId: e687d2aba5fbc268) #24 pc 0x7dcbc libhermes.so (BuildId: bfc3354f8b4e76ab0d2380931fc7ee910123118f) #25 pc 0x7d634 libhermes.so (BuildId: bfc3354f8b4e76ab0d2380931fc7ee910123118f) #26 pc 0x840d0 libhermes.so (BuildId: bfc3354f8b4e76ab0d2380931fc7ee910123118f) #27 pc 0x94eb4 libhermes.so (BuildId: bfc3354f8b4e76ab0d2380931fc7ee910123118f) #28 pc 0x966c0 libhermes.so (BuildId: bfc3354f8b4e76ab0d2380931fc7ee910123118f) #29 pc 0x95ed0 libhermes.so (BuildId: bfc3354f8b4e76ab0d2380931fc7ee910123118f) #30 pc 0xc9f24 libhermes.so (BuildId: bfc3354f8b4e76ab0d2380931fc7ee910123118f) #31 pc 0x71e6c libhermes.so (BuildId: bfc3354f8b4e76ab0d2380931fc7ee910123118f) #32 pc 0x71cc4 libhermes.so (BuildId: bfc3354f8b4e76ab0d2380931fc7ee910123118f) #33 pc 0x72d90 libhermes.so (BuildId: bfc3354f8b4e76ab0d2380931fc7ee910123118f) #34 pc 0x2666c libhermes_executor.so (BuildId: e687d2aba5fbc268) #35 pc 0xaa6e8 libreactnativejni.so (BuildId: 14ee6efbdde7d22c) #36 pc 0xab9e4 libreactnativejni.so (BuildId: 14ee6efbdde7d22c) #37 pc 0x80f74 libreactnativejni.so (BuildId: 14ee6efbdde7d22c) #38 pc 0x15e84 libfbjni.so (BuildId: 27496b9e5551bff5c79496b936b663bf8868c68b) #39 pc 0x15dfc libfbjni.so (BuildId: 27496b9e5551bff5c79496b936b663bf8868c68b) #40 pc 0x15db0 libfbjni.so (BuildId: 27496b9e5551bff5c79496b936b663bf8868c68b) #41 pc 0x75196c boot-framework.oat (BuildId: 1bd20e67c28e6056fc13f44fcec213c008cd3095) #42 pc 0x7af923ad74 #43 pc 0x7550f8 boot-framework.oat (BuildId: 1bd20e67c28e6056fc13f44fcec213c008cd3095) #44 pc 0x1375b8 libart.so (BuildId: d959f7764f0c7e197333334aa9fc1681) #45 pc 0x14600c libart.so (BuildId: d959f7764f0c7e197333334aa9fc1681) #46 pc 0x2e370c libart.so (BuildId: d959f7764f0c7e197333334aa9fc1681) #47 pc 0x7af9af1884 #48 pc 0x2de96c libart.so (BuildId: d959f7764f0c7e197333334aa9fc1681) #49 pc 0x7afa0e8b9e #50 pc 0x5a3e2c libart.so (BuildId: d959f7764f0c7e197333334aa9fc1681) #51 pc 0x5a882c libart.so (BuildId: d959f7764f0c7e197333334aa9fc1681) #52 pc 0x5ccffc libart.so (BuildId: d959f7764f0c7e197333334aa9fc1681) #53 pc 0x12e0fc libart.so (BuildId: d959f7764f0c7e197333334aa9fc1681) #54 pc 0x7afa0e8b9e #55 pc 0x131994 libart.so (BuildId: d959f7764f0c7e197333334aa9fc1681) #56 pc 0x5ccffc libart.so (BuildId: d959f7764f0c7e197333334aa9fc1681) #57 pc 0x7afa661f55 #58 pc 0x2e84e4 libart.so (BuildId: d959f7764f0c7e197333334aa9fc1681) #59 pc 0x2b4a20 libart.so (BuildId: d959f7764f0c7e197333334aa9fc1681) #60 pc 0x5ccffc libart.so (BuildId: d959f7764f0c7e197333334aa9fc1681) #61 pc 0x7afa661f55 #62 pc 0x5ccffc libart.so (BuildId: d959f7764f0c7e197333334aa9fc1681) #63 pc 0x7afa661f55
same here, that’s my
app/build.gradle
file (about the paths: we are using monorepo)react native: 0.63.3
we are using the react native 63 version and getting the crashes on crashlytics. libc.so missing.
Hello everyone! In general, for about half a year I encountered similar errors and even wrote to the Hermes team. As it turned out, all errors are different, and each one needs to be dealt with separately. But given that Hermes does not have native logs at least until RN 0.63.4, this is impossible.
The problem was solved by replacing the engine with a V8 from Google. I have been testing for 2 days, for 6000 users, every single error has been eliminated. And no new ones have even appeared) So anyone interested can try. The transition is as simple as possible and did not cause any problems. Is that slightly increased the size of the universal apk. But with aab, the size for the user hasn’t changed. (https://github.com/Kudo/react-native-v8) By the way, by comparison, it is even better in terms of RAM consumption!
P.S. And sorry for my bad english.
switching to hermes will not solve the issue i have hermes enabled but still i see this crash, hope this gets addressed in next update.
I see it’s mostly happening on Android 7.0 or 7.1.1
@haozhutw Hi. We have been using v8 for more than a year, so far there have been no problems. Debugging via chrome works. The only thing is that when a new version of RN is released, you have to wait several days for a new version of v8 for it and, as mentioned above, a slightly increased size of the application. But otherwise, we are completely satisfied with the work.
@JerakRus Thanks for letting me know! I’ve also switched to
v8-android-nointl
. No crashes so far! Performance is good. The app size increased by only a few megabytes (using app bundle).react: 16.11.0 react-native: 0.62.2 react-native-firebase/analytics: 7.6.10 react-native-firebase/app: 8.4.7 react-native-firebase/crashlytics: 10.4.1
libc.so unknown
@amit-harjani Did you find solution?
@RodolfoGS I’m seeing the same error, did upgrading those help?
We are also getting the same issues. I am adding here logs from the bugsnag:
Unhandled error SIGABRT: Abort program
Location /apex/com.android.runtime/lib64/bionic/libc.so:536816 - abort
Here is the bugsnag logs for the same:
0 libc.so +0x830f0 abort 1 libc.so +0xe7edc __fortify_fatal(char const*, …) 2 libc.so +0xe757c HandleUsingDestroyedMutex(pthread_mutex_t*, char const*) 3 libc.so +0xe7430 pthread_mutex_lock 4 libc++_shared.so +0xc5d78 std::__ndk1::mutex::lock() 5 librealm.so +0x3b0614 0x7c753bb618 6 libhermes_executor.so +0x24740 facebook::jsi::DecoratedHostObject::~DecoratedHostObject() 7 libhermes.so +0x74a58 0x7d510c0a5c 8 libhermes.so +0x7f298 0x7d510cb29c 9 libhermes.so +0x1301fc 0x7d5117c200 10 libhermes.so +0x131b88 0x7d5117db8c 11 libhermes.so +0x131420 0x7d5117d424 12 libhermes.so +0x131290 0x7d5117d294 13 libhermes.so +0x7d5f8 0x7d510c95fc 14 libhermes.so +0x7af04 0x7d510c6f08 15 libhermes_executor.so +0x23de4 non-virtual thunk to facebook::jsi::RuntimeDecorator<facebook::jsi::Runtime, facebook::jsi::Runtime>::collectGarbage(std::__ndk1::basic_string<char, std::__ndk1::char_traits, std::__ndk1::allocator >) 16 libhermes_executor.so +0x27664 facebook::react::JSIExecutor::handleMemoryPressure(int) 17 libreactnativejni.so +0xb49f0 0x7d50cd09f4 18 libreactnativejni.so +0x89c14 0x7d50ca5c18 19 libfbjni.so +0x17eac facebook::jni::detail::MethodWrapper<void (facebook::jni::JNativeRunnable:😃(), &facebook::jni::JNativeRunnable::run, facebook::jni::JNativeRunnable, void>::dispatch(facebook::jni::alias_ref<facebook::jni::detail::JTypeFor<facebook::jni::HybridClass<facebook::jni::JNativeRunnable, facebook::jni::JRunnable>::JavaPart, facebook::jni::JRunnable, void>::_javaobject>) 20 libfbjni.so +0x17dfc facebook::jni::detail::FunctionWrapper<void ()(facebook::jni::alias_ref<facebook::jni::detail::JTypeFor<facebook::jni::HybridClass<facebook::jni::JNativeRunnable, facebook::jni::JRunnable>::JavaPart, facebook::jni::JRunnable, void>::_javaobject>), facebook::jni::detail::JTypeFor<facebook::jni::HybridClass<facebook::jni::JNativeRunnable, facebook::jni::JRunnable>::JavaPart, facebook::jni::JRunnable, void>::_javaobject*, void>::call(_JNIEnv*, _jobject*, void ()(facebook::jni::alias_ref<facebook::jni::detail::JTypeFor<facebook::jni::HybridClass<facebook::jni::JNativeRunnable, facebook::jni::JRunnable>::JavaPart, facebook::jni::JRunnable, void>::_javaobject>)) 21 base.odex +0x16b428 art_jni_trampoline 22 boot-framework.oat +0x734e58 android.os.Handler.dispatchMessage 23 base.odex +0x2052f0 com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage 24 boot-framework.oat +0x73846c android.os.Looper.loop 25 base.odex +0x205518 com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run 26 boot.oat +0x1a5164 java.lang.Thread.run 27 libart.so +0x137330 art_quick_invoke_stub 28 libart.so +0x145fe8 art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*) 29 libart.so +0x4b13f0 art::(anonymous namespace)::InvokeWithArgArray(art::ScopedObjectAccessAlreadyRunnable const&, art::ArtMethod*, art::(anonymous namespace)::ArgArray*, art::JValue*, char const*) 30 libart.so +0x4b2504 art::InvokeVirtualOrInterfaceWithJValues(art::ScopedObjectAccessAlreadyRunnable const&, _jobject*, _jmethodID*, jvalue const*) 31 libart.so +0x4f2ec0 art::Thread::CreateCallback(void*) 32 libc.so +0xe689c __pthread_start(void*) 33 libc.so +0x84b68 __start_thread
React Native version 0.73.1
Platforms Android
JavaScript runtime Hermes
Workflow React Native
Architecture Paper (Old Architecture)
Build type Release app & production bundle
Device Real device
Device model brand: Castles manufacturer Castles model S1E2L osName android osVersion 10 runtimeVersions { “androidApiLevel”: “29”, “osBuild”: “1.4.1.129511” }
We also get this crash sometimes and there is no WebView in our app.
You can add a patch for
react-native-youtube-iframe
where it is trying to use webview@marf Can you try this in your webview component <WebView … androidLayerType=“hardware” />
Also, try to disable animation when you navigate to page with a webview component
Couldn’t found any solution yet, here are the crashlytics logs. Crashed: Thread: SIGABRT 0x0000000000000000 #00 pc 0x531f4 libc.so (BuildId: dc4001c2ef2dfc23467040797a96840c) #01 pc 0x531c4 libc.so (BuildId: dc4001c2ef2dfc23467040797a96840c) #02 pc 0x6f365c libart.so (BuildId: 4c9b59b74ca9272f710a71137164c349) #03 pc 0x16ea8 libbase.so (BuildId: 420d56eac27a210c92900f3ddb760c86) #04 pc 0x16450 libbase.so (BuildId: 420d56eac27a210c92900f3ddb760c86) #05 pc 0x37da5c libart.so (BuildId: 4c9b59b74ca9272f710a71137164c349) #06 pc 0x372dc0 libart.so (BuildId: 4c9b59b74ca9272f710a71137164c349) #07 pc 0x2ac5d8 libart.so (BuildId: 4c9b59b74ca9272f710a71137164c349) #08 pc 0x3731b0 libart.so (BuildId: 4c9b59b74ca9272f710a71137164c349) #09 pc 0x36d324 libart.so (BuildId: 4c9b59b74ca9272f710a71137164c349) #10 pc 0x386148 libart.so (BuildId: 4c9b59b74ca9272f710a71137164c349) #11 pc 0x3778e4 libart.so (BuildId: 4c9b59b74ca9272f710a71137164c349) #12 pc 0x3a0b84 libart.so (BuildId: 4c9b59b74ca9272f710a71137164c349) #13 pc 0x39e330 libart.so (BuildId: 4c9b59b74ca9272f710a71137164c349) #14 pc 0x5817f0 libart.so (BuildId: 4c9b59b74ca9272f710a71137164c349) #15 pc 0x5816f8 libart.so (BuildId: 4c9b59b74ca9272f710a71137164c349) #16 pc 0x48476c libart.so (BuildId: 4c9b59b74ca9272f710a71137164c349) #17 pc 0x70f89504 #18 pc 0x711e918653
I tried disabling androidHardwareAccelerationDisabled by setting it to true and still the crashes happen
Dear SurajMDurgad, but which value of the new property androidLayerType should I use? hardware? Will it resolve the issue?
@jocoders When I made this comment the webview was on 10.9.2,
androidHardwareAccelerationDisabled
isn’t deprecated in that version, either downgrade to that version or useandroidLayerType
as suggested here - https://github.com/react-native-webview/react-native-webview/blob/master/docs/Reference.md#androidhardwareaccelerationdisabledYeah, it also makes my WebView content invisible…
@chrisglein this actually happened twice when i was not using hermes.
No problem. I’m a bit better with the iOS side of things but still tried to help.