Pipeline builds failed on my Android Repo

Aaron_김윤호

My android project is bigger and bigger.

I faced the OOM exception.

<span>Exception in thread "Daemon client event forwarder" java.lang.OutOfMemoryError: Java heap space</span>

<span>at java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.addConditionWaiter(AbstractQueuedSynchronizer.java:1896)</span>

<span>at java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2114)</span>

<span>at java.base/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:458)</span>

<span>at org.gradle.launcher.daemon.server.exec.DaemonConnectionBackedEventConsumer$ForwardEvents.getNextEvent(DaemonConnectionBackedEventConsumer.java:72)</span>

<span>at org.gradle.launcher.daemon.server.exec.DaemonConnectionBackedEventConsumer$ForwardEvents.run(DaemonConnectionBackedEventConsumer.java:59)</span>

<span>ERROR:R8: java.lang.OutOfMemoryError: Java heap space</span>

<span>> Task :myproj:minifyStageReleaseWithR8 FAILED</span><span>> Task :myproj:minifyStageReleaseWithR8</span>

 

So I increased the heap size:

org.gradle.jvmargs=-Xmx4096m -XX:MaxPermSize=1024m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8

 

But It failed with:

Container 'Build' exceeded memory limit.

 

My `.yml` file is:

image: androidsdk/android-30

 

pipelines:

  custom:

    QA:

      - parallel:

        - step:

          name: Build APK

          size: 2x

          script:

            - echo "$KEYSTORE_FILE_BASE64" | base64 -d > android-signing-keystore.jks

            - ./gradlew clean assembleStageRelease

in case of
* low heap size -> OOM

* large heap size -> exceeded memory limit

What should I do?

Theodora Boudale

Hi @Aaron_김윤호,

The maximum memory that can be configured for a Pipelines build in our own infrastructure is 8GB with the size: 2x option. We have a feature request for the ability to increase that limit:

• https://jira.atlassian.com/browse/BCLOUD-17260

You can add your vote and comment there if you're interested in this feature.

If the build cannot be configured to use less than 8GB of memory, you can look into using Runners in one of your servers and run this step on a runner:

• https://support.atlassian.com/bitbucket-cloud/docs/runners/

Runners allow you to run builds in Pipelines on your own infrastructure, and you won’t be charged for the build minutes used by your self-hosted runners. With a runner, it is possible to configure up to 32GB (8x) of memory to run your builds,

Kind regards,
Theodora