https://kotlinlang.org logo
Title
d

dwursteisen

11/28/2018, 11:10 AM
When running my build with gradle 5.0, I got an OOM. Reverting to 4.10.2 fix the issue. I try with another project. I got the same issue. Always with integration test (I don’t know if it’s relacted: my guess is that it’s more memory consuming). Is someone notice a similar issue? What can I do to investigate a bit more of this issue?
e

eskatos

11/28/2018, 11:14 AM
Default memory settings changed in 5.0. You might have to set your build memory requirement explicitly, see https://docs.gradle.org/5.0/userguide/upgrading_version_4.html#rel5.0:default_memory_settings
d

dwursteisen

11/28/2018, 11:28 AM
hum. in the gradle.properties of the project:
org.gradle.jvmargs=-Xmx2048M
Regarding your link: (thanks to point me to this, I skip this yesteday I think...))
All workers, including compilers and test executors, now start with 512MB of heap.
It start with 512 but it’s not the maximum of memory it can consume? (ie: I don’t have to set anything so it can consume more)
e

eskatos

11/28/2018, 2:40 PM
It’s the default max for workers. So yes, you have to increase it on the relevant tasks, e.g. JavaCompile or Test