From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

`export JAVA_TOOL_OPTIONS="-XX:+HeapDumpOnOutOfMemoryError"` may work

The heap dump profiling option takes a heap dump at the end of the build, which probably is fine as well. Note that when you do `org.gradle.jvmargs=-XX:+HeapDumpOnOutOfMemoryError`, then those are all the JVM args for the daemon. So you might want to add some memory settings there as well.

How often do you need to run the scenario until you run out of memory?

usually it fails around 6th build (+ 3 warmups before)

I suppose a heap dump before it runs out of memory would already help, right?

yeah, one build before should be enough :thinking_face:

I’d run the build from the command line manually and then get a heap dump from it.

Or maybe simpler: Use heap dump profiling in Gradle profiler and run enough warmup builds so the profiled build is the last build which would pass.