react-native: enableHermes on React Native 0.60.3 is extremely slow.

I am using 0.61.1, it’s very slow, please let me know how to solve this. after completing this app, I’ll never work on react native.

fuck react native

@BartJanvanAssen thanks for the reply but we no longer do React Native (Flutter is far far superior) 😎😎

Closing after several months without followup from the author. Please make sure to fill in the issue template if you decide to file a new issue.

I lost hours trying to improve my app performance and now im here. ☹️

@ollydixon This is what I’ve got so far:

It seems that loading hermes is the fallback for when loading JSC fails, which is why our apps crash with that error message, since hermes wasn’t setup at all due to enableHermes: false and there’s no further error-handling in this case.

In order to fix the initial problem, I added the following to the android-level build.gradle-file:

maven {
    // Android JSC is installed from npm
    url("$rootDir/../node_modules/jsc-android/dist")
}

./gradlew clean after that, and my issues go away in the sense that I can properly opt out of using Hermes.

I’m not really sure what changed when it comes to how JSC is loaded, but I might try to make sense of that this weekend, I’m a bit too pressed by other deadlines to further look into it right now.

Here’s what my files look like right now: android/app/build.gradle:

...
project.ext.react = [
    entryFile: "index.js",
    jsBundleDirRelease: "$buildDir/intermediates/merged_assets/release/out",
    enableHermes: false,  // clean and rebuild if changing
    hermesCommand: "../../node_modules/hermes-engine/%OS-BIN%/hermes",
]

def jscFlavor = 'org.webkit:android-jsc:+'
def enableHermes = project.ext.react.get("enableHermes", false);
...
dependencies {
    ....
    if (enableHermes) {
      def hermesPath = "../../node_modules/hermesvm/android/";
      debugImplementation files(hermesPath + "hermes-debug.aar")
      releaseImplementation files(hermesPath + "hermes-release.aar")
    } else {
      implementation jscFlavor
    }
    ...
}

android/build.gradle:

...
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 {
            // Android JSC is installed from npm
            url("$rootDir/../node_modules/jsc-android/dist")
        }
        google()
    }
}
...

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.

Hermes only slow on Debug mode, on a release build it’s much faster and i can reduce my app from ~40MB to 17MB.

Experiencing similar issues, though I’m using RN 0.60.4.

I’ve been having similar issues. A regex heavy task which took 3-5 seconds with hermes enabled took 40-50 seconds with hermes enabled!
With @Zloka 's suggestion I was able to disable Hermes and saved myself from tearing my hair out!

I’m using Hermes in “true” in RN 0.60.6 and it works extremely fast. Now my app loads 2x faster that when Hermes was in “false”. (Release mode)

@Zloka I can’t revert back from hermes now otherwise the SoLoader fails. The project is stuck now, any ideas?

@ollydixon This is what I’ve got so far:

It seems that loading hermes is the fallback for when loading JSC fails, which is why our apps crash with that error message, since hermes wasn’t setup at all due to enableHermes: false and there’s no further error-handling in this case.

In order to fix the initial problem, I added the following to the android-level build.gradle-file:

maven {
    // Android JSC is installed from npm
    url("$rootDir/../node_modules/jsc-android/dist")
}

./gradlew clean after that, and my issues go away in the sense that I can properly opt out of using Hermes.

I’m not really sure what changed when it comes to how JSC is loaded, but I might try to make sense of that this weekend, I’m a bit too pressed by other deadlines to further look into it right now.

Here’s what my files look like right now: android/app/build.gradle:

...
project.ext.react = [
    entryFile: "index.js",
    jsBundleDirRelease: "$buildDir/intermediates/merged_assets/release/out",
    enableHermes: false,  // clean and rebuild if changing
    hermesCommand: "../../node_modules/hermes-engine/%OS-BIN%/hermes",
]

def jscFlavor = 'org.webkit:android-jsc:+'
def enableHermes = project.ext.react.get("enableHermes", false);
...
dependencies {
    ....
    if (enableHermes) {
      def hermesPath = "../../node_modules/hermesvm/android/";
      debugImplementation files(hermesPath + "hermes-debug.aar")
      releaseImplementation files(hermesPath + "hermes-release.aar")
    } else {
      implementation jscFlavor
    }
    ...
}

android/build.gradle:

...
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 {
            // Android JSC is installed from npm
            url("$rootDir/../node_modules/jsc-android/dist")
        }
        google()
    }
}
...

Looks like i got it working on the 0.61.5 version. i failed to fill the android/build.gradle file correctly… I did change the file but notice i had 2 places where i had to change the maven config 1st place is the allprojects => repositories. the second one is the buildscript => repositories. i forgot the first one and kept on searching for days for this to fix… maybe i can help someone 😉

I just upgraded to React Native 0.60.5 just to try Hermes because my Android app was really slow, but it made my app to go from slow to ultra slow. It’s totally unusable with Hermes enabled.

Hello Guys, I tried this line of code in /android/app/build.gradle and it works configurations.all { resolutionStrategy { force "com.facebook.soloader:soloader:0.8.2" } }

Thanks @Arshimonde. I tried this but it didn’t help me:

• Without hermes, the app with 0.63.3 is about 10 times slower than the app with 0.59.9 (https://github.com/facebook/react-native/issues/30403)
• With hermes it is even slower (with 0.63.3, it is about 50% slower than without hermes)

@wmonecke it’s not an issue with RN though it’s more that it’s not a container. It will always have significant platform bugs introduced by Android manufacturers and iOS updates and Android API changes. This isn’t the case with Flutter since it effectivity runs on it’s own engine.

I found that over the years, RN was pushing extremely broken and immature updates and using technologies that were new or not completed. For people who develop apps for multiple companies it was becoming a huge time sink to be on top of this. Also the navigation is still horrid. Debugging on Android is useless. Etc etc

Not only that; be we picked up hundreds of bugs across Android manufactures and design inconsistencies with our RN projects; which was the straw that broke the camels back.

If you’re a professional developer, my advice is to stay very far from RN and use something like Flutter.

Even Native Android dev is broken; some of the manufacturers override default styles and margins, for example (many other things, like broken standard APIs; look at file management, for example.)

😃

Why react native 0.63 very slow .?

@ollydixon This is what I’ve got so far: It seems that loading hermes is the fallback for when loading JSC fails, which is why our apps crash with that error message, since hermes wasn’t setup at all due to enableHermes: false and there’s no further error-handling in this case. In order to fix the initial problem, I added the following to the android-level build.gradle-file:

maven {
    // Android JSC is installed from npm
    url("$rootDir/../node_modules/jsc-android/dist")
}

./gradlew clean after that, and my issues go away in the sense that I can properly opt out of using Hermes. I’m not really sure what changed when it comes to how JSC is loaded, but I might try to make sense of that this weekend, I’m a bit too pressed by other deadlines to further look into it right now. Here’s what my files look like right now: android/app/build.gradle:

...
project.ext.react = [
    entryFile: "index.js",
    jsBundleDirRelease: "$buildDir/intermediates/merged_assets/release/out",
    enableHermes: false,  // clean and rebuild if changing
    hermesCommand: "../../node_modules/hermes-engine/%OS-BIN%/hermes",
]

def jscFlavor = 'org.webkit:android-jsc:+'
def enableHermes = project.ext.react.get("enableHermes", false);
...
dependencies {
    ....
    if (enableHermes) {
      def hermesPath = "../../node_modules/hermesvm/android/";
      debugImplementation files(hermesPath + "hermes-debug.aar")
      releaseImplementation files(hermesPath + "hermes-release.aar")
    } else {
      implementation jscFlavor
    }
    ...
}

android/build.gradle:

...
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 {
            // Android JSC is installed from npm
            url("$rootDir/../node_modules/jsc-android/dist")
        }
        google()
    }
}
...

Looks like i got it working on the 0.61.5 version. i failed to fill the android/build.gradle file correctly… I did change the file but notice i had 2 places where i had to change the maven config 1st place is the allprojects => repositories. the second one is the buildscript => repositories. i forgot the first one and kept on searching for days for this to fix… maybe i can help someone 😉

After an hour or two of bashing my head against the wall, this comment fixed my issue. Thanks! I didn’t realise it was the bottom section that needed the fix.

@ollydixon Yup, just noticed I have the same issue when I figured I’d forego using hermes for now. Application builds just fine, but crashes on launch with the following output:

2019-08-12 13:02:27.866 14055-14082/fi.mafynetti.mafyclient E/SoLoader: couldn't find DSO to load: libhermes.so
2019-08-12 13:02:27.867 14055-14082/fi.mafynetti.mafyclient E/AndroidRuntime: FATAL EXCEPTION: create_react_context
    Process: fi.mafynetti.mafyclient, PID: 14055
    java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
        at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:738)
        at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:591)
        at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:529)
        at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:484)
        at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java:20)
        at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create(HermesExecutorFactory.java:27)
        at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:949)
        at java.lang.Thread.run(Thread.java:764)

same error in react-native 0.63.0

Android 5.0.2 Device Galaxy A5 Release 2015 6 third party Native plugin react-native v 0.61.2

It get launch in 8 seconds.

Wow very slow, how can I faster it

0.65.1 with hermes debug builds seems to be extremely slow in Android. Not just the startup time, but the ui is super slow.

😂 ok. In other words, dont post inflammatory and condescending comments on an open source project. This is on a personal level. 😃

All the best and stay safe,

Walter Monecke

On Sat, May 8, 2021, 16:46 Oliver Dixon @.***> wrote:

@ollydixon https://github.com/ollydixon It seems you have an opinion and I congratulate you! I have 50K MAU and very few bugs. To each, his own.

It’s not an opinion it’s based of hard data. You can run a standard warehouse test across 20 different manufacturers for example; they’ll give you video results. Look at how broken RN is on some of those manufacturers. Firebase has cloud testing warehouses you can monkey run; you can see tons of inconsistencies and crashes with RN and even native Android dev 😃

Hope this helps you find bugs 🐜

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/facebook/react-native/issues/25986#issuecomment-835389858, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFZB7VLF6KH3CIZTLALN3RLTMVFGFANCNFSM4IKL7NLQ .

@ollydixon It seems you have an opinion and I congratulate you! I have 50K MAU and very few bugs. To each, his own.

It’s not an opinion it’s based of hard data. You can run a standard warehouse test across 20 different manufacturers for example; they’ll give you video results. Look at how broken RN is on some of those manufacturers. Firebase has cloud testing warehouses you can monkey run; you can see tons of inconsistencies and crashes with RN and even native Android dev 😃

Hope this helps you find bugs 🐜

Guys we don’t need comments like the ones left by @cisplRejjak or @ollydixon. React Native is open-source after all and if you are so incompetent to deactivate it / upgrade to the next stable version then the problem might be you. If you bash the RN team or post condescending comments for these types of issues, then I pray for your coworker’s health and sanity.

@Anujmoglix Same here !!

@baotoan1905 if you’ve already built your app at least once, clean the build running this:

$ cd android && ./gradlew clean

@ecreeth: Thanks for your replying. I have figured it out. It was because of that previously I got issue app crash when generating app bundle in release mode, to deal with it I had to add exclude ‘**/libjscexecutor.so’ to section packagingOptions like bellow. After comment it out, it works if I want to disable hermes.

Any updates?

I have Also Performance issue with the Hermes Enabled on RN 0.60.4 on android devices, it extremely slow on debug build and take 2-3 second on click on a static button, Please Suugest me any Solution, But it works fine on IOS devices

Maybe related https://github.com/facebook/hermes/issues/111#issuecomment-533313121 If you are doing a lot of string concatenate, I suggest using v8 instead of hermes at the moment

Same issues here, updating from RN 0.59 to ~0.60 caused serious performance issues for my project. Disabling hermes helped a bit, but performance was still noticeably degraded, we just had to roll back to 0.59 for now.

iOS builds were not effected

try enable debug mode, there no issue on release build