Raise MAX_VM_MEMORY
Alan Bateman
Alan.Bateman at oracle.com
Sun Sep 16 07:04:04 PDT 2012
On 16/09/2012 13:39, Henri Gomez wrote:
> For some days, I got OOM in Javadoc stages for jdk8 and lambda on Linux
>
> I think others build OpenJDK 8 on 32bits systems could be in same
> trouble and I suggest to raise it from 612m to 768m.
>
>
> --- jdk/make/docs/Makefile.orig 2012-09-16 14:38:19.714697484 +0200
> +++ jdk/make/docs/Makefile 2012-09-16 14:38:26.767697710 +0200
> @@ -73,7 +73,7 @@
> else ifeq ($(ARCH),universal)
> MAX_VM_MEMORY = 1024
> else
> - MAX_VM_MEMORY = 612
> + MAX_VM_MEMORY = 768
> endif
>
> # List of all possible directories for javadoc to look for sources
This was increased to 768m a few weeks ago, see:
http://hg.openjdk.java.net/jdk8/jdk8/jdk/rev/7dda50fe8e1c
so you probably just need to sync up your clone of jdk8/jdk8. It looks
like the change that pushed it over the limit this time went into
jdk8/jdk8 with the same integration that that increased the limit so
surprising to hear you are running into this with jdk8/jdk8.
For Lambda then I assume it's just the additional APIs mean that javadoc
needs more memory than when building the javadoc for jdk8. We had to
increase it in jigsaw/jigsaw a while back too.
-Alan.
More information about the jdk8-dev
mailing list