Reduce Xmx in .jvmopts and build.sbt #2605
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Another attempt at fixing OOM's in build
So the .jvmopts sets max memory to 6G AND the (one) forked jvm for tests also sets memory to 6G (which by default would receive the same settings anyway, btw). So if my maths is correct, that‘s 12G in total on a machine that IIRC is only 7.5G.
So set .jvmopts to 3G and the forked JVM javaopts to also 3G
Supporting issue :
scalatest/scalatest#770,
NB:
„...to cap the memory for the main process + the forked process to be < 3G at any point of time. That would mean:
main process + SBT forked process + debugger process in test (if you created)
should not be > 3G“
„...providing the memory caps on the main process, forked, process, and children worked.“
Note that, if you follow the links, the same issue is reported for specs2 and also on laptops - ie not just on travis.