Getting SIGABRT Crash on release build. libc.so #29978

afkcodes · 2020-09-18T19:48:41Z

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

The text was updated successfully, but these errors were encountered:

SConaway · 2020-09-20T00:08:37Z

Are you running this on Android or on linux?

Side note: you may want to upgrade your installation of @react-native-community/cli, as seen here.

afkcodes · 2020-09-20T09:09:40Z

@SConaway Its on Android and the crash happens on an Android device.

SConaway · 2020-09-20T17:08:52Z

Are there other any details of the crash logs?

Try upgrading the cli

afkcodes · 2020-09-20T17:10:53Z

@SConaway i am not seeing any thing more abou the crash, i will surely update the cli and put a new build and see how it goes thanks for help.

SConaway · 2020-09-20T17:11:47Z

No problem. I'm a bit better with the iOS side of things but still tried to help.

JerakRus · 2020-10-01T10:18:30Z

@ashishfeels
Hi, did you manage to solve the problem? We have something similar happening on devices of users in production

afkcodes · 2020-10-03T06:47:56Z

@JerakRus i havent gave an update so cant tell much about it.will let you know when i do

chrisglein · 2020-10-06T18:57:06Z

Do you have any information to indicate this is a React Native core issue? Have you looked at the Hermes repo to see if there's anything there? Does it repro without Hermes?

afkcodes · 2020-10-07T04:03:08Z

@chrisglein this actually happened twice when i was not using hermes.

nikDemyankov · 2020-10-15T17:42:50Z

Hi. We've started to get the same crash in crashlytics after releasing new version with target sdk set to 29 (before it was 28). Effecting mainly Android 10 (80% of all crashes) and Android 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 [email protected].

afkcodes · 2020-10-15T18:26:29Z

What i have found out that almost all of the crashes in my case is happening in Redmi/Mi Devices.

safaiyeh · 2020-10-20T03:43:29Z

Hi @nikDemyankov thanks for a bit more context. It is hard to pinpoint the specific issue, is there more information you could provide? Which components? Which user interaction lead to this? etc?

RodolfoGS · 2020-10-31T22:06:13Z

Same issue on react-native: 0.63.3

Crashed: Thread :  SIGSEGV  0x0000000000000010
#00 pc 0x7de39e0748 libjsc.so 
#01 pc 0x7de3a2cfe8 libjsc.so 
#02 pc 0x7ef3e8b0c8 libc.so

SConaway · 2020-10-31T22:08:18Z

@RodolfoGS

Just a shot in the dark, but what is your Android SDK setup? Meaning, what is the output of react-native info in your project? What SDK tools are specified in either android/build.gradle or android/app/build.gradle?

RodolfoGS · 2020-10-31T22:11:03Z

@SConaway react-native info

System:
    OS: macOS 10.15.5
    CPU: (4) x64 Intel(R) Core(TM) i7-5557U CPU @ 3.10GHz
    Memory: 31.79 MB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 14.13.0 - /usr/local/bin/node
    Yarn: 1.19.1 - /usr/local/bin/yarn
    npm: 6.14.8 - /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.0, DriverKit 19.0, macOS 10.15, tvOS 14.0, watchOS 7.0
    Android SDK:
      Android NDK: 21.3.6528147
  IDEs:
    Android Studio: 4.0 AI-193.6911.18.40.6514223
    Xcode: 12.0/12A7209 - /usr/bin/xcodebuild
  Languages:
    Java: 12.0.1 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: ~0.63.3 => 0.63.3
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

SConaway · 2020-10-31T22:33:51Z

@RodolfoGS What is your android/build.gradle (this matters since it says how you're building the app)?

marf · 2023-11-07T14:25:50Z

Same issue here, 70% of crashes come from Motorola, 51% on Android 10

Crashed: Thread: SIGABRT  0x0000000000000000
#00 pc 0x1cca6 libc.so (BuildId: 274d521cac67401dfe4aa994475b77fc)
#01 pc 0x5f5150 libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#02 pc 0x820db libc++.so (BuildId: 6b3370a19feb51e665b53a480ddc37d8)
#03 pc 0xa6496 libc.so (BuildId: 274d521cac67401dfe4aa994475b77fc)
#04 pc 0x2fb41 libc++.so (BuildId: 6b3370a19feb51e665b53a480ddc37d8)
#05 pc 0x82163 libc++.so (BuildId: 6b3370a19feb51e665b53a480ddc37d8)
#06 pc 0x2fcd9 libc++.so (BuildId: 6b3370a19feb51e665b53a480ddc37d8)
#07 pc 0x82163 libc++.so (BuildId: 6b3370a19feb51e665b53a480ddc37d8)
#08 pc 0x6d657471
#09 pc 0x11a655d boot-framework.oat (BuildId: 5e1cc4441d019c5afa8d2e8d8b2d62d22841af00)
#10 pc 0x8726d libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#11 pc 0xaea2a libc.so (BuildId: 274d521cac67401dfe4aa994475b77fc)
#12 pc 0x5c6c5b libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#13 pc 0xa64ff libc.so (BuildId: 274d521cac67401dfe4aa994475b77fc)
#14 pc 0xc0a09 libGLESv2_mtk.so (BuildId: 23371600ff687c5d5b164ed8c7b974f4)
#15 pc 0x3dba85 libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#16 pc 0x4089b libc++.so (BuildId: 6b3370a19feb51e665b53a480ddc37d8)
#17 pc 0x3ddfb9 libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#18 pc 0x7872d libc.so (BuildId: 274d521cac67401dfe4aa994475b77fc)
#19 pc 0x5d7ce4 libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#20 pc 0x3ddbf1 libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#21 pc 0x667dfa libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#22 pc 0x5e01a4 libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#23 pc 0x5d7ce4 libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#24 pc 0x3ddb85 libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#25 pc 0x3dd879 libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#26 pc 0x667dbe libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#27 pc 0x3dd54d libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#28 pc 0x51407 libc.so (BuildId: 274d521cac67401dfe4aa994475b77fc)
#29 pc 0xb2439 libglslcompiler.so (BuildId: 6019b75c800d401b8881608b712cb9ae)
#30 pc 0xb2439 libglslcompiler.so (BuildId: 6019b75c800d401b8881608b712cb9ae)
#31 pc 0x4b3f3 libc.so (BuildId: 274d521cac67401dfe4aa994475b77fc)
#32 pc 0xb2436 libglslcompiler.so (BuildId: 6019b75c800d401b8881608b712cb9ae)
#33 pc 0x667dbe libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#34 pc 0x51407 libc.so (BuildId: 274d521cac67401dfe4aa994475b77fc)
#35 pc 0x5a9699 libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#36 pc 0x5a9699 libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#37 pc 0x4b3f3 libc.so (BuildId: 274d521cac67401dfe4aa994475b77fc)
#38 pc 0x3dcc31 libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#39 pc 0x667dbe libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#40 pc 0x51407 libc.so (BuildId: 274d521cac67401dfe4aa994475b77fc)
#41 pc 0x5a9697 libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#42 pc 0x5a9697 libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#43 pc 0x7d1cb libc++.so (BuildId: 6b3370a19feb51e665b53a480ddc37d8)
#44 pc 0x7cfa1 libc++.so (BuildId: 6b3370a19feb51e665b53a480ddc37d8)
#45 pc 0x7d1cb libc++.so (BuildId: 6b3370a19feb51e665b53a480ddc37d8)
#46 pc 0x7cfa1 libc++.so (BuildId: 6b3370a19feb51e665b53a480ddc37d8)
#47 pc 0x5f5116 libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#48 pc 0x7cd8f libc++.so (BuildId: 6b3370a19feb51e665b53a480ddc37d8)
#49 pc 0x3e97b libc++.so (BuildId: 6b3370a19feb51e665b53a480ddc37d8)
#50 pc 0x3f055 libc++.so (BuildId: 6b3370a19feb51e665b53a480ddc37d8)
#51 pc 0x3ed9f libc++.so (BuildId: 6b3370a19feb51e665b53a480ddc37d8)
#52 pc 0x67ac22 libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#53 pc 0x42db7a libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#54 pc 0x5f5156 libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#55 pc 0x5f5129 libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#56 pc 0x5f511c libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#57 pc 0x42dbe3 libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#58 pc 0x67abfe libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#59 pc 0x3eac3 libc++.so (BuildId: 6b3370a19feb51e665b53a480ddc37d8)
#60 pc 0x5f5116 libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#61 pc 0x67ac22 libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)
#62 pc 0x7cb6f libc++.so (BuildId: 6b3370a19feb51e665b53a480ddc37d8)
#63 pc 0x42db7a libhwui.so (BuildId: 44892cf1d3b767ae16acd27951c5b0d4)

CostasCF · 2023-12-06T20:09:13Z

Same here, in production some users experienced this problem, react-native 0.72.6

mrand15 · 2023-12-20T03:11:12Z

Now seeing this issue after having upgraded from 0.69 -> 0.72. This is now responsible for the vast majority of crashes in the application. Also hermes enabled.

So far unable to reproduce

Reporting stats show it's happening across a wide range of devices, and different android versions

Will try upgrading to the 0.73 if that doesn't work may need to consider downgrading the RN version until a solution is found.

rizshivalli · 2024-03-07T08:14:29Z

Getting this crash in plenty of users in production

Crashed: Thread: SIGABRT  0x0000000000000000
#00 pc 0x534d4 libc.so (BuildId: 65f0a078b7cc159a5d3df081e44378ff)
#01 pc 0x534a4 libc.so (BuildId: 65f0a078b7cc159a5d3df081e44378ff)
#02 pc 0x3dfb0 libc.so (BuildId: 65f0a078b7cc159a5d3df081e44378ff)

trucuit · 2024-03-28T04:36:33Z

same crash

Crashed: Thread: SIGABRT 0x0000000000000000
#00 pc 0x51698 libc.so (BuildId: 6697743033c2bdf7b5a5571266b37e03)
#1 pc 0x51668 libc.so (BuildId: 6697743033c2bdf7b5a5571266b37e03)
#2 pc 0x41670 libc.so (BuildId: 6697743033c2bdf7b5a5571266b37e03)
#3 pc 0x41d88 libc.so (BuildId: 6697743033c2bdf7b5a5571266b37e03)
#4 pc 0x41ea0 libc.so (BuildId: 6697743033c2bdf7b5a5571266b37e03)
#5 pc 0x47b3c libc.so (BuildId: 6697743033c2bdf7b5a5571266b37e03)
#6 pc 0x435fc libc.so (BuildId: 6697743033c2bdf7b5a5571266b37e03)
#7 pc 0x6d1a4 libhermes.so (BuildId: 19cf666039ce5d2aeca3909963853ad955e8839d)
#8 pc 0x34a3c libhermes.so (BuildId: 19cf666039ce5d2aeca3909963853ad955e8839d)
#9 pc 0x2eee8 libhermes.so (BuildId: 19cf666039ce5d2aeca3909963853ad955e8839d)
#10 pc 0x20ea4 libhermes-executor-release.so (BuildId: 6f924153575b2297a9b489c75d3834bd885ae749)

paryanihitesh · 2024-03-29T10:02:23Z

@marf Are you using webview in your app?

marf · 2024-03-29T10:05:09Z

Yes, we are also using a web view. Marco Fontana On 29 Mar 2024, at 11:02, paryanihitesh ***@***.***> wrote: @marf<https://github.com/marf> Are you using webview in your app? — Reply to this email directly, view it on GitHub<#29978 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AADWRPSOYHCBQ6FFM72FP2DY2U34NAVCNFSM4RSN7CCKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBSG4YDCMBVGU3A>. You are receiving this because you were mentioned.Message ID: ***@***.***>

paryanihitesh · 2024-03-29T10:11:11Z

@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

felansu · 2024-03-29T10:16:12Z

Im using react-native-youtube-iframe, that requires react-native-webview 😮‍💨

    "react-native-webview": "^13.7.0",
    "react-native-youtube-iframe": "2.3.0",

paryanihitesh · 2024-03-29T10:27:42Z

You can add a patch for react-native-youtube-iframe where it is trying to use webview

afkcodes · 2024-03-30T17:58:59Z

just letting you know @felansu this crash is not related to iframes or webview, i did not use any of them

marf · 2024-03-31T13:39:51Z

@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

We use a webview only on a specific page of our app that it is not accessed by lot of users so I do not thing the webview is the cause of those crashes since they happen for a lot of our users.

williamgurzoni · 2024-03-31T18:03:27Z

We also get this crash sometimes and there is no WebView in our app.

boontawatk · 2024-04-04T06:41:57Z

I've found that mine occurs only on older Android versions (around 7 and 8). I'm quite sure this problem is not associated with WebView.

marf · 2024-04-04T08:18:08Z

I've found that mine occurs only on older Android versions (around 7 and 8). I'm quite sure this problem is not associated with WebView.

Same for us, we see most of the crashes coming from Android 7

vatsal-gadhiya-searce · 2024-04-20T07:05:10Z

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" }

mrand15 · 2024-06-24T03:57:04Z

We've now resolved these crashes in our project.
In our case, the cause ended up being a 3rd party SDK which introduced a memory leak at the native level.
An absolute nightmare to debug, as the crash logs provide no useful info as to the culprit.
Removing the SDK with the memory leak resolved the crashes.

felansu · 2024-06-26T10:43:27Z

We've now resolved these crashes in our project. In our case, the cause ended up being a 3rd party SDK which introduced a memory leak at the native level. An absolute nightmare to debug, as the crash logs provide no useful info as to the culprit. Removing the SDK with the memory leak resolved the crashes.

can we know the name of the 3rd party SDK are you using?

mrand15 · 2024-07-05T04:43:51Z

can we know the name of the 3rd party SDK are you using?

Suffice to say it was used (among other things) for native crash monitoring and reporting (ironic), disabling this feature also seemed to resolve the memory leaks in the SDK. We've been told other customers haven't reported this issue yet, so it may have just been a unique interaction with our app.

404-html · 2024-07-19T08:54:12Z

After trying different solutions we finally managed to get rid of this issue.

What was causing the issue?
The app was basically running into infinite loop. In our case, when the phone was going offline (high likely your case is different!), each network request was failing. We were logging each failed network request by, sending another network request! Which of course was failing, and causing cascading set of events. When reproducing, the app was freezing, and after a while crashing. So basically a poor design.

What (really) helped to track the issue?
Google Analytics Events. When using Firebase Crashalytics with Google Analytics events are listed in "Logs and breadcrumbs" tab:

By looking at different logs of this error we found a pattern: an event for app going offline is present in pretty much every occurrence. This is how we found the cause.

Summarizing
Having an app covered with tracking events, and using analytics tool that syncs after crash, might help you finding a real cause of this issue.

trungledangAxonActive · 2024-07-19T09:30:10Z

Hi @afkcodes. Would you mind if I ask you a question that what was the engine that you used that caused happening twice this issue? Thank you so much.
I guess you used JSC.

a-petrenko-muse · 2024-08-29T12:16:45Z

Same error on 0.74.5, was fine on 0.72.12

afkcodes · 2024-08-29T15:24:56Z

@trungledangAxonActive i actually dont remember it now its been 4 years now

CrazyStoneJy · 2024-08-30T02:59:28Z

same error 0.73.1

SGamrekelashvili · 2024-08-31T17:17:49Z

same problem after upgrading 75.2, ram is free >100 always at crash time

drumsSandoval · 2024-11-25T05:46:36Z

Same Error in v0.76.3

Alexandre-Cornillon · 2024-11-25T15:49:27Z

same error on 74.6

gulshercb7 · 2024-12-16T06:43:24Z

same issue any luck ?
"react-native": "0.76.2"

afkcodes added the Needs: Triage 🔍 label Sep 18, 2020

react-native-bot added the Platform: Linux Building on Linux. label Sep 18, 2020

chrisglein added Tech: Hermes Hermes Engine: https://hermesengine.dev/ Needs: Author Feedback Platform: Android Android applications. and removed Needs: Triage 🔍 labels Sep 22, 2020

github-actions bot added Needs: Attention Issues where the author has responded to feedback. and removed Needs: Author Feedback labels Oct 3, 2020

chrisglein added Needs: Author Feedback and removed Needs: Attention Issues where the author has responded to feedback. labels Oct 6, 2020

github-actions bot added Needs: Attention Issues where the author has responded to feedback. and removed Needs: Author Feedback labels Oct 7, 2020

safaiyeh added Needs: Author Feedback and removed Needs: Attention Issues where the author has responded to feedback. labels Oct 20, 2020

N3TC4T added this to Xaman App May 10, 2024

N3TC4T moved this to Backlog - To be determined in Xaman App May 10, 2024

Getting SIGABRT Crash on release build. libc.so #29978

Getting SIGABRT Crash on release build. libc.so #29978

Comments

afkcodes commented Sep 18, 2020 • edited Loading

Description

React Native version:

Steps To Reproduce

Expected Results

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

SConaway commented Sep 20, 2020

afkcodes commented Sep 20, 2020

SConaway commented Sep 20, 2020

afkcodes commented Sep 20, 2020

SConaway commented Sep 20, 2020

JerakRus commented Oct 1, 2020

afkcodes commented Oct 3, 2020

chrisglein commented Oct 6, 2020

afkcodes commented Oct 7, 2020

nikDemyankov commented Oct 15, 2020

afkcodes commented Oct 15, 2020

safaiyeh commented Oct 20, 2020

RodolfoGS commented Oct 31, 2020

SConaway commented Oct 31, 2020

RodolfoGS commented Oct 31, 2020

SConaway commented Oct 31, 2020 • edited Loading

marf commented Nov 7, 2023 • edited Loading

CostasCF commented Dec 6, 2023

mrand15 commented Dec 20, 2023 • edited Loading

rizshivalli commented Mar 7, 2024

trucuit commented Mar 28, 2024

paryanihitesh commented Mar 29, 2024

marf commented Mar 29, 2024 via email

paryanihitesh commented Mar 29, 2024

felansu commented Mar 29, 2024

paryanihitesh commented Mar 29, 2024 • edited Loading

afkcodes commented Mar 30, 2024

marf commented Mar 31, 2024

williamgurzoni commented Mar 31, 2024

boontawatk commented Apr 4, 2024

marf commented Apr 4, 2024 • edited Loading

vatsal-gadhiya-searce commented Apr 20, 2024

mrand15 commented Jun 24, 2024 • edited Loading

felansu commented Jun 26, 2024

mrand15 commented Jul 5, 2024 • edited Loading

404-html commented Jul 19, 2024

trungledangAxonActive commented Jul 19, 2024 • edited Loading

a-petrenko-muse commented Aug 29, 2024

afkcodes commented Aug 29, 2024

CrazyStoneJy commented Aug 30, 2024

SGamrekelashvili commented Aug 31, 2024

drumsSandoval commented Nov 25, 2024

Alexandre-Cornillon commented Nov 25, 2024

gulshercb7 commented Dec 16, 2024

afkcodes commented Sep 18, 2020 •

edited

Loading

SConaway commented Oct 31, 2020 •

edited

Loading

marf commented Nov 7, 2023 •

edited

Loading

mrand15 commented Dec 20, 2023 •

edited

Loading

paryanihitesh commented Mar 29, 2024 •

edited

Loading

marf commented Apr 4, 2024 •

edited

Loading

mrand15 commented Jun 24, 2024 •

edited

Loading

mrand15 commented Jul 5, 2024 •

edited

Loading

trungledangAxonActive commented Jul 19, 2024 •

edited

Loading