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

Gradle Community

Hi <@UAJKMRD2Q>,
Thanks for testing the change. Having options to set workers memory size makes sense. So if you are willing to provide a PR go ahead.

:thumbsup:  will look into this the next few days

<@U02DF9JDXJM> Here you go: <https://github.com/gradle/gradle/pull/20198>

Thank you. I checked it quickly and it looks good. The only comment I have right now is that memory parameter description might deserve a format, but I can add that small change myself. I will look more into it tomorrow.

<@UAJKMRD2Q> does OOM happen on every build or is it kinda random? I am wondering if a big sourceset is a key factor here  or maybe there is some memory leak that we need to fix. Is that issue reproducible on some public project? Either way, that doesn’t affect the PR and new parameters

it happens on a specific subproject of our build that has by far the largest sourceSets