-
Notifications
You must be signed in to change notification settings - Fork 24.2k
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
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) libjsc.so still occuring on Caterpillar S41 (Android 8.0) #25494
Comments
@ebaynaud
|
Sorry but no, I cannot reproduce by myself because I don't have this device within easy reach. The crash is coming from Google Play console. |
Hi Kudo, I confirm crash is gone from Samsung devices but after upgrading to 0.59.10 we are still seeing it on a couple of other devices as well (unfortunately also through Google Play - I don't have access to such a device to reproduce). So far I've seen it on: Running Android 6.0, 7.0 and 8.0. I've also seen a couple of devices running Android 9 or Android 8.1: As you can see, Huawei devices are standing out. I have a Huawei P smart (FIG-LX1) running android 8.0 test device myself but it seems to be running just fine on that one.
|
I'm experiencing it as well on a Huawei Y5 (2017). |
Same here. Asus ZenFone 3 Max, Android 8.1.
|
Seeing potentially similar issue for a variety of 64-bit phones running Android 9.
|
I'm seeing this on at least 5 different devices. Anyone came up with a solution? |
@N1ghtly If you have the ability to do so, it might be worth trying to upgrade to 0.60.4 and turn Hermes on. See @Kudo's comment here: |
We're also seeing crashes on our build, w/ JSC r245459... @Kudo i attempted to symbolicate using your instructions from #25494 (comment), and here's what I came up with:
|
We can confirm that the same issue occurs on beyondx (Samsung Galaxy S10 5G) on Android 9, which has an Exynos 9820 (ARMv8.2):
|
Thank you all and especially @dhess-zynga providing symbolicated backtrace. |
@Kudo Please publish a JIT disabled JSC for us to try out. Unfortunately Hermes isn't an option for some of us yet until intl support is added: facebook/hermes#23 |
I can confirm crashes on a Huawei Mate 20 Pro running RN 0.59.10:
|
Hello ! I just updated my application on the PlayStore today, I use now the RN version 0.59.10, and I have this problem on a device. I saw this on the Google Play Console. The device is Galaxy S8+ (dream2lte) on Android 9.
|
I've also saw similar crashes on multiple devices in Google Play Store crash report. RN: 0.59.10
backtrace:
|
We see it intermittently as well...
https://github.com/facebook/hermes/blob/master/doc/Features.md Despite heroic efforts to track it down/fix it from @Kudo and folks, it might be worth going backward vs. forward to before 0.59, when the JSC was upgraded. We like trying to stay updated on features, but crashes/freezing/etc. on production apps that we can't stop are making us consider waiting until 0.60+/Hermes is more mature to actually have hooks, etc. that came with 0.59+. |
Hey guys, I've found what caused the problem in our app. we are using react-navigation in combination with useScreens. There seems to be a problem in the useScreens code: software-mansion/react-native-screens#105 deactivating and removing useScreens seems to fix the crashes |
Can confirm that I too use react-navigation but not using useScreens. |
Hey, Same as @mars-lan , using react-navigation 3.0.0 but not useScreens. |
We also use react-navigation (3.7.1) as well—but similar to the other folks here, don't use useScreens. One of our early theories was something with navigation (since it seemed to happen more often when we interacted with navigation elements). We had cleared it later after seeing other reports that seemed to say they didn't have it, but will test on our side and see if it resolves it. |
We have released React Native 0.60.4 on Wednesday using Hermes on Android and I can confirm there are no more 64-bit crashes (at least not yet at this point). In fact, Hermes improved our average app boot time from 5.8s to 2.5s or even less on higher end devices. One thing to note: If you support Android 4 you should use the latest version of "hermes-engine" (0.1.1) as the current "hermesvm" (0.1.0) integration in React Native 0.60.4 makes the app crash on boot time. See facebook/hermes#42 for more info on that. |
Hi all. Updated:Well, it is my fail. This is a crash not because of JSC but because of a problem with portrait mode in SDK 26 (android 8) |
Same crash hapening for me as well F/libc (14838): Fatal signal 11 (SIGSEGV) in tid 14959 (mqt_js) |
Hey guys, this appears to be absolute blocker for all Android apps using React Native to be updated since Google Play not allow to push apps without 64 bit support from Aug 1. And we can't go back to previous RN versions since they don't support 64 bit at all. Am I missing something? Please correct. It's not clear if anybody from React Native team aware of that. Is there any way to escalate this issue? |
|
every version is having that issue |
@RodolfoGS i can confirm that. i'm having that exact same issue me too ! |
We had some success in reducing these native crashes by eliminating 3rd party dependencies (Instabug and Smartlook were causing some in our case). We also had a reduction in crashes by eliminating use of animated value listeners. Turns out that AnimatedValue.addListener is incredibly expensive even if your callback does zero work. If you have more than 5 listeners active at once it can cause all sorts of strange crashes in native and java, break the debugger, cause hangs, and generally wreak havoc with no indication that it's the source of the problem.... IMO after going through a long ordeal to figure out the source of this issue I think that addListener should be marked as experimental or log a warning any time it's used. It's not safe or stable to use. We also switched to hermes and had lots of crashes and hangs there until we resolved the above issue with animated value listeners. Now the app is much more stable, fast, and lightweight on hermes. tl;dr -- remove your 3rd party deps and remove animated value listeners first and then try hermes and your issues may disappear |
Hermes doesn't seems to be a good replacement for JSC, because the app starts to consume 2 times more memory and looking into comments above it even does not guaranty the fix. That issue definitely requires more attention and support. |
Apologies if this is white noise but I don't see any mention of animated WebViews here when they seem to be a common theme with this error. react-native-webview/react-native-webview#429 The following code produces the signal 11 crash every time in our app when the default react-navigation animation is enabled. Two things prevent the crashing, 1) removing the WebView from the first scene (not an option for us), or 2) removing the animation by using the animationEnabled:false option. <AppStack.Navigator There is a lot of chat in the wild about AdMob bringing apps down when it randomly inserts adverts containing WebViews. The crashing was happening consistently on the following in our test device:
|
@adbs1 Can you explain more about this? |
@RodolfoGS Very late here so I'll leave you these: invertase/react-native-firebase#2935 (comment) |
Same issue in RN 0.63.4, React 16.13.1 |
If having issue with react-native-webview check this comment webview#575 |
Hi @zuhairnaqi, I'm having that issue but I'm using admob, and I think that sometimes they show ads on a webview, but I haven't options to disable hardware acceleration in the admob library, I'm using Do you know how can I disable hardware acceleration there? Thanks, |
@RodolfoGS Sorry don't know and never used this library |
Switching to v8 fixed the problem for me! No crashes so far. |
@trizin Could you help me How to switch to v8? |
@ttkien Sure, it's pretty simple. You need to install the package and modify your |
Summary: Upgrade jsc-android to latest stable version. Hopefully this should finally fix facebook#25494. Before Hermes totally replaced JSC, it should be worth to have this and make JSC stable ## Changelog [Android] [Changed] - Upgrade jsc-android to 250230.2.1 Pull Request resolved: facebook#31304 Test Plan: Launch app with new jsc-android and see everything works fine. Reviewed By: TheSavior Differential Revision: D28630503 Pulled By: yungsters fbshipit-source-id: 84510f91c81d4aaefe265d5492677ad6ff10e0fe
Summary: Upgrade jsc-android to latest stable version. Hopefully this should finally fix facebook#25494. Before Hermes totally replaced JSC, it should be worth to have this and make JSC stable ## Changelog [Android] [Changed] - Upgrade jsc-android to 250230.2.1 Pull Request resolved: facebook#31304 Test Plan: Launch app with new jsc-android and see everything works fine. Reviewed By: TheSavior Differential Revision: D28630503 Pulled By: yungsters fbshipit-source-id: 84510f91c81d4aaefe265d5492677ad6ff10e0fe
Summary: Upgrade jsc-android to latest stable version. Hopefully this should finally fix #25494. Before Hermes totally replaced JSC, it should be worth to have this and make JSC stable ## Changelog [Android] [Changed] - Upgrade jsc-android to 250230.2.1 Pull Request resolved: #31304 Test Plan: Launch app with new jsc-android and see everything works fine. Reviewed By: TheSavior Differential Revision: D28630503 Pulled By: yungsters fbshipit-source-id: 84510f91c81d4aaefe265d5492677ad6ff10e0fe
I am still getting this error, any solution? Samsung Galaxy S8+ signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) pid: 0, tid: 0 >>> com.myapp<<< backtrace: |
for me it was that I was using the wrong version of Hermes for my project. You can look up the correct version for you here https://github.com/facebook/hermes/releases Hope it helps! |
How to solve the following problems?
Android 10 (SDK 30) signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0000000000000010 pid: 0, tid: 0 >>> com.myapp<<< #00 pc 00000000000f7748 /data/app/com.xxx.xxx-RyQEpiqg2bYRiq2ThRjaag==/lib/arm64/libjsc.so (_ZNK3JSC10AccessCase20propagateTransitionsERNS_11SlotVisitorE+16) |
Same as #24261 but still occuring on device Caterpillar S41 (Android 8.0).
React Native version: 0.59.10
The text was updated successfully, but these errors were encountered: