Go 1.13

seems to have fixed it.

2 Likes

Thank you soooooo much!

I was going crazy over this. I tried:

env.JAVA_TOOL_OPTIONS  
-XX:+UnlockExperimentalVMOptions  
-XX:+UseCGroupMemoryLimitForHeap
-Xmx10g
-XX:MaxMetaspaceSize=10g 

So I was setting the wrong env var and missed Xms.

How did you get to that? Experience and/or better google-fu? Just asking in the hopes of picking up something useful for the future.

And as to why this problem appeared now: Is my assumption reasonable that it is some side-effect of the new setup Jakob mentioned?

It’s down to changed defaults in the new gradle version.

I found this by looking at the parameters visible on the command line when gradle wrapper launches the gradle java process during build. Not sure why this doesn’t happen when building locally.

The builds are now flaky in a different way (stream closed etc), but atleast it builds after a few goes.