Hey all, sorry if a bit OT. I noticed yesterday the Gradle daemon is crashing on my GitHub Action wh...

# gradle

[Davide Giuseppe Farella]

Hey all, sorry if a bit OT.
I noticed yesterday the Gradle daemon is crashing on my GitHub Action while building an Android release.
Didn't do any major change, beside update AGP, Kotlin, Compose, etc, which were already pretty recent, so minor updates.
Am I the only one experiencing this?

[Davide Giuseppe Farella]

FAILURE: Build failed with an exception.

* What went wrong:
Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed)

* Try:

Run with --stacktrace option to get the stack trace.

Run with --info or --debug option to get more log output.

Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Task cinescoutcinescout-utilscinescout utils composemergeExtDexDebugAndroidTest

Task cinescoutcinescout-utilscinescout utils composecompileDebugAndroidTestKotlin

##[error***Process completed with exit code 1.

[tapchicoma]

try to limit workers count on CI

[mbonnin]

Or give your daemon overlord more RAM 😈

[Davide Giuseppe Farella]

@tapchicoma Could that be given by the parallelization of building many modules?

[tapchicoma]

yes

[Davide Giuseppe Farella]

Makes sense, I got like 50 🙂
org.gradle.workers.max=?
20?

[Davide Giuseppe Farella]

I see from doc:

Default is number of CPU processors.

So should I limit to like 2? 🤔

[tapchicoma]

the more parallel build - the faster it will finish, but will require more RAM. So check what Github agent has and tune accordingly

[Davide Giuseppe Farella]

Makes sense 🙂 Thank you

[Davide Giuseppe Farella]

I remembered I have 8GB of memory for JVM in my gradle.properties , while Ubuntu/Win has 7GB available on GitHub Actions, so I changed that to 4 on CI and it seems ok now 🙂