-
Notifications
You must be signed in to change notification settings - Fork 24.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Android] intermittent crash A/libc: Fatal signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 0x72609e9760 in tid 19730 (mqt_js), pid 19470 #33124
Comments
+1 |
Have you tried switching over to Hermes? |
This happens to me as well but apparently only when Hermes is disabled. Didn’t test on real device only emulator |
@cortinico I haven't. On the current project, we had no plans to use Hermes for now, since it's not very stable yet... But it looks like RN is dropping support for jsc-android? Would there be any other solution to this? |
That's actually not true IMHO. We're usign Hermes in production on a variety of products and works greatly for us. We're also looking into having hermes as default in react-native for the majority of users:
That's also not true. We're not going to support using external engines. Can I ask you where you got this information from? If it's in our documentation I'd like to update it. cc @neildhar for visibility. |
@cortinico no worries, it was simpliy my feeling. And I noticed that Hermes is pushed through very actively. But some projects are not planning to move to Hermes just yet because they might have legacy, etc. For example, on iOS it doesn't support Intl... However, would you be able to help with the issue above (without enabling Hermes)? |
Sadly not. That's a native crash that it's really hard to debug. I was suggesting a switch of the JS engine as this feels like a simple change that can potentially resolve this isssue |
I see... I can imagine Hermes will bring other issues as well. @cortinico |
@ilyagru Given that the crash is in libjsc.so, there's a reasonable chance you're running into a bug in JSC, particularly if it clears after switching to Hermes. On the point of iOS Intl specifically, it's something we're working on making available as part of the effort to make Hermes the default engine. |
Same issue. Any solution? |
I getting this crash every time I perform reload, and enable debug. Happens after upgrading to latest RN version and newArchEnabled set to true - both emulator and android. after I set newArchEnabled to false, seems like no longer getting this issue (at least during development, app is not for release yet atm) |
Since upgrade RN to 0.68 with Hermes enable, no more crash for me on android simulator with M1 Mac. |
+1 Facing the same issue for so many days. Running 0.68.1 version of react native. Tried running by disabling Hermes still this crash occurs on launch of app in android |
fwiw, we switched to Hermes for Android and crash rate dropped dramatically. This particular crash hasn't happened since. |
Any solution? I have the same error, I have M1 Chip with arm64-v8a emulator. ABI: arm64-v8a |
Same here, can't continue working on the project.. ABI: arm64-v8a |
Same problem. |
same problem, this suddenly appear |
any solution on this problem? |
@zverexe in my case, switching to Hermes helped |
@aklevko I am using Realm. and it's does not support hermes in this time, so sad |
Same issue, Hermes does not help. 0.69.x does not help. Tends to happen upon manual reloads. For us it seems like this error is preceded by:
For us it's like every second reload until we enabled And if the debugger is paused when the reload occurs then the chance of a crash appears to be nearly 100%. |
Same problem, with version 0.69.6. |
+1 |
for me it's fixed after enabling hermes in apple m1 chip. hope it helps someone |
@kesavan49 , did u used Realm react-native, Realm developer say that not compative with Hermes(android). So I still using Flipper |
Thank you! It seems to have worked for me too. I just needed to add this to my
I was having this issue with a M1 Pro chip and react-native v0.64.3 |
Those are hard to debug. Is there any recommended steps that would help to investigate and resolve this type of crashes? |
@fukemy NO i am not using realm react native. In our case it was working perfectly intel based machine but when we switch to M1 based chip we got this error. After enableing hermes it got removed. Thanks |
enabling herms fixed this issue on mac M1 and RN 0.68.2 |
To reiterate, Hermes does not fix our issue - but I guess that's the fix for Mac M1. |
I actually had Hermes enabled by default but am still seeing this issue on my M1 mac |
This actually happens to us as well. We are on M2 Macs running in the emulator. Debug mode crashes very frequently. After a project cleaning as per others suggested sometimes it gets better, sometimes it is the same. Turning on |
This comment was marked as resolved.
This comment was marked as resolved.
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue was closed because it has been stalled for 7 days with no activity. |
Description
I am experiencing a crash on Android which occurs randomly, sometimes at the launch, sometimes later on some screen, so it's difficult to provide steps to reproduce. The logs are not very helpful either. This crash might be relevant only to arm64-v8a + mac M1 combination. Occurs on both emulator and real devices, though. One assumption was about the
jsc-android
packge. Could you please take a look? At least to point any direction where the source might be?I'm attaching all the logs and info that I have.
Thank you!
Originally posted to react-native-community/jsc-android-buildscripts#160
Logs
Sentry reports
On Sentry it is reported like so:
or
Symbolicated
Unsymbolicated
Click to expand!
Log file
crash.pdf
Version
0.66.4
Output of
npx react-native info
Hermes enabled: false
jsc-android: 250230.2.1
ABI: arm64-v8a
React Native: 0.66.4
macOS 12.1 M1 Pro
Android Emulator: Pixel 4 API 30
System:
OS: macOS 12.1
CPU: (10) arm64 Apple M1 Pro
Memory: 3.94 GB / 32.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 17.0.1 - /opt/homebrew/bin/node
Yarn: 1.22.17 - /opt/homebrew/bin/yarn
npm: 8.1.0 - /opt/homebrew/bin/npm
Watchman: 2021.11.08.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.11.2 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Android SDK:
API Levels: 28, 29, 30, 31
Build Tools: 29.0.2, 30.0.2, 30.0.3, 31.0.0
System Images: android-29 | Google Play ARM 64 v8a, android-30 | Google Play ARM 64 v8a, android-30 | Google Play Intel x86 Atom_64, android-31 | Google APIs ARM 64 v8a
Android NDK: Not Found
IDEs:
Android Studio: 2021.1 AI-211.7628.21.2111.8092744
Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_312 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.66.4 => 0.66.4
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
The issue occurs randomly so it's difficult to provide steps to reproduce.
Snack, code example, screenshot, or link to a repository
No response
The text was updated successfully, but these errors were encountered: