Apologies - this is my first time here. I can't find an answer for this anywhere. I'd like to know how I can override this hardcode here DefaultWorkerProcessBuilder.java#L251-L251, for GradleWorkerMain threads - specifically for tests? I'm getting OOM on the worker when running unit tests. I've tried setting DEFAULT_JVM_OPTS, JAVA_OPTS, GRADLE_OPTS, modifying DEFAULT_JVM_OPTS in gradlew/gradlew.bat, and have tried stuff like this in my build.gradle.kts:

tasks.withType<JavaExec>().configureEach {
    jvmArgs("-Xmx1024m")
}

tasks.withType<Test>().configureEach {
    jvmArgs("-Xmx1024m")
}

...and nothing takes. Thanks.

I assume the worker is a github worker? I've never had to tweak... are you using the gradle setup action?

This is actually on my local MacOS, but we are running into the same problem on GHA build too.

if it's failing on your macos WITHOUT trying to constrain the memory I'd say you have a memory leak and need to start tracing the memory

It is throwing OutOfMemory exception

what is it

Running unit tests. Here you go ex:

~/csvol/git/wavebid-a2o/wavebid-a2o-service:1195> ./gradlew test 
OpenJDK 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended

Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "mysql-cj-abandoned-connection-cleanup"
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with message can't create name string at open/src/java.instrument/share/native/libinstrument/JPLISAgent.c line: 838
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with message can't create name string at open/src/java.instrument/share/native/libinstrument/JPLISAgent.c line: 838
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with message can't create name string at open/src/java.instrument/share/native/libinstrument/JPLISAgent.c line: 838
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with message can't create name string at open/src/java.instrument/share/native/libinstrument/JPLISAgent.c line: 838

Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "DefaultDispatcher-worker-14"

Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "DefaultDispatcher-worker-12"
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with message can't create name string at open/src/java.instrument/share/native/libinstrument/JPLISAgent.c line: 838

looks like java, have you tried setting the memory to like 4g and seeing what it does?

Yes.

ok, I'd recommend looking at it with jprofiler or something like jprofiler

The upper Java runtimes all take the parameters we set. And those seem to be okay. It is the workers that are hardwired to -Xmx512m that give us trouble.

yeah, idk, sorry

Another, just to document here. This is the one I was getting consistently yesterday...

org.gradle.api.internal.tasks.testing.TestSuiteExecutionException: Could not complete execution for Gradle Test Executor 3.
	at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.stop(SuiteTestClassProcessor.java:65)
	at java.base@21/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
	at java.base@21/java.lang.reflect.Method.invoke(Method.java:580)
	at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
	at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
	at org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:33)
	at org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:92)
	at jdk.proxy1/jdk.proxy1.$Proxy4.stop(Unknown Source)
	at org.gradle.api.internal.tasks.testing.worker.TestWorker$3.run(TestWorker.java:200)
	at org.gradle.api.internal.tasks.testing.worker.TestWorker.executeAndMaintainThreadName(TestWorker.java:132)
	at org.gradle.api.internal.tasks.testing.worker.TestWorker.execute(TestWorker.java:103)
	at org.gradle.api.internal.tasks.testing.worker.TestWorker.execute(TestWorker.java:63)
	at org.gradle.process.internal.worker.child.ActionExecutionWorker.execute(ActionExecutionWorker.java:56)
	at org.gradle.process.internal.worker.child.SystemApplicationClassLoaderWorker.call(SystemApplicationClassLoaderWorker.java:121)
	at org.gradle.process.internal.worker.child.SystemApplicationClassLoaderWorker.call(SystemApplicationClassLoaderWorker.java:71)
	at app//worker.org.gradle.process.internal.worker.GradleWorkerMain.run(GradleWorkerMain.java:69)
	at app//worker.org.gradle.process.internal.worker.GradleWorkerMain.main(GradleWorkerMain.java:74)
Caused by: java.lang.OutOfMemoryError: Java heap space

Hi, you can increase the heap allocation for the test process using:

maxHeapSize = "1G"

https://docs.gradle.org/current/dsl/org.gradle.api.tasks.testing.Test.html#org.gradle.api.tasks.testing.Test:maxHeapSize

jvmArgs

does not include system properties and the minimum/maximum heap size. Full example:

dependencies {
    testImplementation("org.junit.jupiter:junit-jupiter:5.7.1")
    testRuntimeOnly("org.junit.platform:junit-platform-launcher")
}

tasks.named<Test>("test") {
    useJUnitPlatform()

    maxHeapSize = "1G"

    testLogging {
        events("passed")
    }
}

Thanks. I will try that.

I work w/ James. Nice side effect is that tests are over twice as fast now.