App Crash on Android OS 6 Samsung Galaxy S7 SM-G930FD (JSC Crash) 64 bit support A/libc: Fatal signal 11 (SIGSEGV) #24261
Comments
dishantwalia
changed the title
dishantwalia
changed the title
|
Thanks for submitting your issue. Can you take another look at your description and make sure the issue template has been filled in its entirety? 👉 Click here if you want to take another look at the Bug Report issue template. |
react-native-bot
added
Ran Commands
Updated |
|
Logcat Error Screenshot for reference |
|
publishing 64bit split build I'm also getting this crash on launch on Galaxy S7 & Galaxy S7 Edge with Android 7.0 on Crashlytics for those devices I'm getting: the workaround of only providing 32bit build is solving this for now |
|
I'm seeing the exact same errors as @nadavmos on Galaxy S7 running Android 7.0. The app is crashing at startup |
@nsantacruz are you also using react-navigation? seems common to all other reporters |
|
@nadavmos The crash is not related to |
|
@hramos @mkonicek As of now we can conclude that this seems to be an issue with latest RN 0.59 release, affecting android builds running on |
|
Also happening on 0.58.5. Galaxy S7. Android 6.0. Setting it to 32 bit build is also not working. |
|
We're observing the same crashes on 64 bit builds of RN 0.59.4 on a Galaxy S7 running Android 7.0. Sadly we don't have access to that model of device. It works fine on all of ours. |
|
Having the same issue with Huawai P9 device under the following environment: This is the Crashlytics stack trace we get: |
|
Having the same issue with Samsung Galaxy S7, on Android 7 |
|
|
|
Thank you for trying to help but the solution has not helped us.
… 16 апр. 2019 г., в 19:12, Andrew Jack ***@***.***> написал(а):
Adding this to your android/app/build.gradle may fix it:
packagingOptions {
pickFirst '**/libjsc.so'
pickFirst '**/libc++_shared.so'
}
See react-native-community/jsc-android-buildscripts#95 <react-native-community/jsc-android-buildscripts#95>
Testing this now.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#24261 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEO_1BMzddSncn2DtQeDcx_y1KIz0ZSGks5vhfaJgaJpZM4cX_xB>.
|
@AndrewJack was it working for you? |
Sadly we already had those in there. We have pulled our 64-bit builds from the Play Store. This may not be related at all to the crash in the 64bit build, but Galaxy S7 devices running the armeabi-v7a build are now crashing a lot as per the below. Immediately upon startup. Really wondering what is so different about the S7 compared to other devices. |
|
@taschik It didn't work, I thought correcting the jsc-android-buildscripts config might work. |
|
I'm getting the same exception and it can't be caught by uncaught exception handler. In my Android app I've tried this code: with handler, which only writes exception name to console and then returns control to default handler, but that code hadn't been executed before the app crash. I was trying to investigate, why Crashlytics doesn't log this exceptions. Maybe that is the reason... I remember, that once or twice I've seen native crashes in my fabric console, so crashlytics is able to log native crashes, but somehow not in this case. |
|
@SpertsyanKM The crash occurs at the ndk level. You won't see the crash in the firebase console, unless you add the Crashlytics NDK library. https://docs.fabric.io/android/crashlytics/ndk.html As you've found the |
|
I upgraded to RN 0.59.5 today and the crash still happens. This issue is not yet fixed. |
Can confirm that this solved the issue for us. 64 bit builds with |
|
I tried the tombstone logging @j-wang mentioned but I've never really used that and it was an immense file which was hard to read, after searching for a while I didn't really seem to find a readable root cause. After taking the advice of @armenbadalyan, I started wondering if it just wasn't something silly in the start of our app and sure enough when removing the first component's UI, I noticed that the app was running again, stable. So after more digging I noticed that a specific component was given issues where an Image was rendered. In that component there is a chance that we pass Might help other people to simplify the first component of their app to make sure it's not crashing on that code. TL;DR: This is probably completely off-topic by now, but to whom it concerns: DON'T USE |
|
@harryt2 yes, me too. I got a huge spike in ANRs after upgraded to RN 0.60.+ |
|
A little help to the ones still trying to address the startup crash:
It doesn't solve the problem but let you find out something more. I've 2 apps, one is working well with the 64 bit, still struggling on the other one even if they've the same configuration. My crashing device is a One Plus 5t (64 bit) |
|
I've just seen this on a new release of our App, building with RN 59.10, specifically on a Samsung Galaxy Note9 on Android 9. Anyone else seeing a similar issue? |
|
@msspshaw As mentioned above and in the other issue, yes. The new JSC freezes/crashes randomly on certain Android devices because it gets non-deterministically garbage collected—then the entire app crashes. The solution is to upgrade to 0.60+ and use Hermes, or switch out JSC for v8. |
+1 Works for me. I had same problems. Thank you! |
|
Also see it happening on a Samsung Galaxy S7 IO-IL 086 on Android 7.0 RN 0.59.10 |
|
@BracketMan Are you using V8 instead of JSC? |
|
@EmilScherdin ahhh no, I am not. Will give it a shot and report back thanks. |
|
@EmilScherdin I can confirm that running on V8 on RN 0.59.10 is working for me, no more crashes. Thanks! |
|
We experience the same issue on RN 0.59.10 with v8. I see that JIT is not disabled for arm64-v8a and on devices with this architecture we have crashes. |
|
@mmamoyco Do you have the stacktrace of the crash from V8? |
|
@Kudo Yeah I do have the crash log. We have shifted to v8 from jsc because we were experiencing a lot of crashes. But the same is happening using v8. below is the log #00 pc 0000000000c31dd8 /data/app/my.app.id-a42vFQTz2lrEJMUnXdYsYA==/lib/arm64/libv8.so |
We had this exact issue on 0.59.1 and were able to fix it by doing the following:
dependencies {
...
+ "jsc-android": "^245459.0.0",
...
}then run
allprojects {
repositories {
mavenLocal()
jcenter()
maven {
// All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
url "$rootDir/../node_modules/react-native/android"
}
+ maven {
+ // Local Maven repo containing AARs with JSC library built for Android
+ url "$rootDir/../node_modules/jsc-android/dist"
+ }
}
}
dependencies {
+ // Make sure to put android-jsc at the top
+ implementation 'org.webkit:android-jsc:+'
compile fileTree(dir: "libs", include: ["*.jar"])
implementation "com.android.support:appcompat-v7:${rootProject.ext.supportLibVersion}"
implementation "com.facebook.react:react-native:+" // From node_modules
}
android {
// ...
+ packagingOptions {
+ pickFirst '**/armeabi-v7a/libc++_shared.so'
+ pickFirst '**/x86/libc++_shared.so'
+ pickFirst '**/x86_64/libc++_shared.so'
+ pickFirst '**/arm64-v8a/libc++_shared.so'
+ pickFirst '**/libjsc.so'
+ }
} |
|
could anybody help to answer this question? |
I hate to just quote you but I nearly missed your solution in the noise of this thread. Thank you so much @YoranRoels!! This saved the day! |
|
I find a Online real machine test website, In there i chose GALAXY S7 Edge and android 7.0 os, Unfortunately it dosen't happen crash, and i try to use @YoranRoels method set |
You are a life saver! ❤️ I've been looking for your answer for three days to paste that code and to change jsc-android version to exactly that you've mentioned. And it's now working! Error happend when I've upgraded RN version from 0.59 to 0.60. The app was broken for only the android, ios was fine. The strangest thing was that app compiled successfully so everything looked great, but when it launched, it crashed immediately. |
…book#25426) Summary: Upgrade bundled jsc-android that should fix the native JSC crash addressed for facebook#24261. Major changes after r241213 are: 1. Disable DFG JIT. 2. Upgrade WebKitGTK to 2.24.2, this version includes the [new bytecode format enhancement](https://webkit.org/blog/9329/a-new-bytecode-format-for-javascriptcore/). 3. Workaround LLVM __clear_cache issue which may have some problems on ARM Cortex A-53. For details, please refer to the PRs in https://github.com/react-native-community/jsc-android-buildscripts. In facebook#24261, there were many experimented JSC deliveries and thank to people in RN community helping me verify the final version which solve the crash issues. ## Changelog [Android] [Fixed] - Upgrade jsc-android to r245459 and fix crash on Samsung S7 Edge Pull Request resolved: facebook#25426 Test Plan: 1. Run [measure scripts](https://github.com/react-native-community/jsc-android-buildscripts/tree/master/measure) on my Samsung Note 5. 2. Provide an [experimented version](https://www.npmjs.com/package/kudo-ci/jsc-android/v/245459.9000.0) for community who previously reported JSC crash and seems no more crashes happened, see that thread in facebook#24261 Differential Revision: D16071388 Pulled By: cpojer fbshipit-source-id: 52eb7af61ccd73db21dea1e2e9c58f191a311868
and others
Bug Report
Crashed on launch
Crashed with only this error log traced on android logcat A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 20217.
To Reproduce
react-native run-android
and navigate to second screen from initial route through stack navigator. I am using
React-Navigation 3.6App crashes as soon as I start going into
react-navigationand crashing inSamsung S7 64 bit CPUdevice, working fine in other android devices which I am using.Expected Behavior
just to work in a stable manner. like in earlier react-native version 0.58
Environment
React Native Environment Info:
System:
OS: Mac OS mojave 10.14
Binaries:
npm: 6.4.1
Android Studio: Version 3.2.1
Android 6.0.1 (real device: Samsung S7 SM-G930FD)
React Native v0.59.3
Temporary Workaround:
When I removed 64 bit ndk filters "arm64-v8a", "x86_64" from ndk abiFilters in defaultConfig block of buidl.gradle by provide only 32 bit support.
It works fine.
The text was updated successfully, but these errors were encountered: