Getting SIGABRT Crash on release build. libc.so #29978
Comments
|
Are you running this on Android or on linux? Side note: you may want to upgrade your installation of |
|
@SConaway Its on Android and the crash happens on an Android device. |
|
Are there other any details of the crash logs? Try upgrading the |
|
@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. |
|
No problem. I'm a bit better with the iOS side of things but still tried to help. |
chrisglein
added
Tech: Hermes
|
@ashishfeels |
|
@JerakRus i havent gave an update so cant tell much about it.will let you know when i do |
github-actions
bot
added
Needs: Attention
|
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? |
chrisglein
added
Needs: Author Feedback
and removed
Needs: Attention
|
@chrisglein this actually happened twice when i was not using hermes. |
github-actions
bot
added
Needs: Attention
|
Hi. We've started to get the same crash in crashlytics after releasing new version with target sdk set to We've tried to reproduce it on different devices and emulators - no luck. Hermes is disabled, running |
|
What i have found out that almost all of the crashes in my case is happening in Redmi/Mi Devices. |
|
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? |
safaiyeh
added
Needs: Author Feedback
and removed
Needs: Attention
|
Same issue on |
|
Just a shot in the dark, but what is your Android SDK setup? Meaning, what is the output of |
|
@SConaway |
|
@RodolfoGS What is your |
|
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 🙏 .
|
|
@variaankitb Did you find a solution? |
|
Couldn't found any solution yet, |
|
any updated? |
github-actions
bot
added
the
Needs: Repro
|
Getting hundreds of this |
|
we were able to narrow down some of the SIGSEGV issues being directly proportional to ANRs |
|
Just saw this in prod on 0.72.4 RN, hermes enabled.
Haven't been able to reproduce myself yet. Crashed: Thread: SIGABRT 0x0000000000000000 |
|
Deployed to production yesterday, today 1 device detected with that problem Error reporting: |
|
Also getting this crash in plenty of users in production since upgrading to React Native 0.72.6. Was not happening as often with React Native 0.71. It seems to happen across different Android versions and different devices (Samsung, Huawei, Motorola, Xiaomi, etc). Most crash reports look similar to this one: |
|
Same issue here, 70% of crashes come from Motorola, 51% on Android 10 |
|
Same here, in production some users experienced this problem, react-native 0.72.6 |
|
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. |
|
Getting this crash in plenty of users in production
|
|
same crash Crashed: Thread: SIGABRT 0x0000000000000000 |
|
@marf Are you using webview in your app? |
|
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: ***@***.***>
|
|
@marf Can you try this in your webview component Also, try to disable animation when you navigate to page with a webview component |
|
Im using |
|
You can add a patch for |
|
just letting you know @felansu this crash is not related to iframes or webview, i did not use any of them |
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. |
|
We also get this crash sometimes and there is no WebView in our app. |
|
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 |
|
We are also getting the same issues. I am adding here logs from the bugsnag: Unhandled error Location Here is the bugsnag logs for the same: 0 libc.so +0x830f0 abort React Native version Platforms JavaScript runtime Workflow Architecture Build type Device Device model |
|
We've now resolved these crashes in our project. |
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. |
and others
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:
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:
The text was updated successfully, but these errors were encountered: