Every build fails with "Received 'killed' signal" during apk build

[tanos92]

Hi,

as the title every build of android apk for my application fails with the message “received killed signal” during gradle task “./gradlew clean assembleDebug --no-daemon --stacktrace”.

Thanks for the help.

[levlaz]

Your build is probably running out memory. Is the exit code 137?

[diegolmello]

It’s happening here as well.
Last week’s builds were running ok.
Today this error started to show.
@levlaz It’s 137, yes, but what can I do to fix it?

14:04:58.502 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
14:04:58.502 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] FAILURE: Build failed with an exception.
14:04:58.502 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
14:04:58.502 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * What went wrong:
14:04:58.502 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] Execution failed for task ':app:bundleReleaseJsAndAssets'.
14:04:58.502 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] > Process 'command 'node'' finished with non-zero exit value 137
14:04:58.502 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
14:04:58.502 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * Try:
14:04:58.502 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] Run with --stacktrace option to get the stack trace.  Run with --scan to get full insights.
14:04:58.509 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
14:04:58.509 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * Get more help at https://help.gradle.org
14:04:58.509 [ERROR] [org.gradle.internal.buildevents.BuildResultLogger]
14:04:58.509 [ERROR] [org.gradle.internal.buildevents.BuildResultLogger] BUILD FAILED in 1m 31s

[tanos92]

There is no exit code

[levlaz]

That is not possible, every single command that runs in Linux will always have an exit code. CircleCI exposes this in the dashboard if you hover over the failed step. It will be on the top right of the build output.

For example:

[levlaz]

137 implies that you are running out of memory.

We wrote a blog post on how to troubleshoot and resolve these sorts of issues: https://circleci.com/blog/how-to-handle-java-oom-errors/

[tanos92]

this is the task that fails with killed signal, there is no exit code on the top right