SIGSEGV crash on Android
See original GitHub issueThis issue seems somewhat related to #6760 , but different enough for a different issue.
The main differences are –
- The crash happens when there are a lot of components (e.g. 1000 Views nested inside each other). But in the particular instance of our app, the crash also happens when there are relatively fewer components (~100) and we receive a 4xx, 5xx level response from a HTTP call. I have not been able to reproduce this in an isolated project with ~100 components and failed HTTP requests.
- I am experiencing the crash when I’m NOT connected to Chrome Debugger. It works fine when connected to the debugger.
All I see is this, without a stack trace whatsoever.
A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0xbbadbeef in tid 27250 (mqt_js)
Since the issue happens when I’m not connected to the debugger, it makes it more serious because I cannot distribute the app. Any leads on how to debug this would be helpful.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:14
- Comments:12 (2 by maintainers)
Top Results From Across the Web
How to figure out the reason of a SIGSEGV in Android
I've been getting increasing number of reports that my android app crashes, the crash happens in native code so a stacktrace isn't produced....
Read more >SIGSEGV crash in libhwui.so on Pixel android 12 only #32547
Description I am getting crashes on android. The crash occur only on Pixel devices in production and only on android 12.
Read more >Diagnosing Native Crashes | Android Open Source Project
The following sections include common types of native crash, an analysis of a sample crash dump, and a discussion of tombstones.
Read more >signal 11 (SIGSEGV), code 2 (SEGV_ACCERR) crash on ...
signal 11 (SIGSEGV), code 2 (SEGV_ACCERR) crash on Android 12 arm64 devices · This case doesn't occur if x264 is built without asm...
Read more >Android signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault ...
Identify which line of code is crashing by adding logcat messages to your code. Then print the pointers to find which has a...
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
I have this issue too, But it works fine when debugging via Chrome
Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we’re automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:
If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.