We randomly get Max Heap Space on our android builds

[joaquinvaz]

If you are looking for help, please confirm the following...

• I confirm I have searched the Docs, Codemagic Sample Projects, and GitHub Discussions.
• I confirm the software versions on my local computer match the ones in CI environment (e.g. Xcode version, Gradle version). See here
• I confirm I am able to do a fresh clone of the repository and build the project on my local computer.

Which mobile framework are you using?

React Native

Steps to reproduce

We get this out of memory error randomly (sometimes it works), and the build fails. Doesn't generate the build. It makes us waste a lot of build minutes.
We have these configs. But they don't seem to work.

gradle.properties:
org.gradle.jvmargs=-Xmx8g -XX:MaxMetaspaceSize=2g -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8

        export NODE_OPTIONS="--max-old-space-size=8192"
        cd android
        ./gradlew app:assembleStaging -PversionCode=$BUILD_NUMBER -PversionName=$VERSION_NAME
        cd ..

The currently configured max heap space is '2 GiB' and the configured max metaspace is 'unknown'.
For more information on how to set these values, please refer to https://docs.gradle.org/8.13/userguide/build_environment.html#sec:configuring_jvm_memory in the Gradle documentation.
To disable this warning, set 'org.gradle.daemon.performance.disable-logging=true'.
Daemon will be stopped at the end of the build after running out of JVM heap space

Expected results

Should run the builds correctly all the time.

Actual results

About 40-50% of the time, builds fail with this error.

Build id (optional)

No response

[icarusdust]

Hi @joaquinvaz, this error is expected because of the fact that your project's Gradle tasks require more powerful machines with more heap space available, so you can switch to M4 or Linux machines with more power that Codemagic offers. I suggest you check this blog for more information. Check this doc page as well.

[icarusdust]

I will close this thread as resolved for now. If you are still facing the same issue, you can re-open it by replying to it.