Re: buildbot -> java.lang.OutOfMemoryError: PermGen space

["Daniel S. Haischt" <da...@googlemail.com>]

The following Maven options seem to fix the issue:

MAVEN_OPTS=-Xmx512m -XX:PermSize=64m -XX:MaxPermSize=256m
-XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=C:\slave4\openejb-trunk-win\dumps

On Thu, Dec 31, 2009 at 3:29 AM, Daniel S. Haischt
<da...@googlemail.com> wrote:
> Hi,
>
> currently the buildbot crashes on a win 2008 server VM with an OOME
> (see subject). We could try adding the the following VM options to
> force a dump being generated. Right now I am unable to find any dumps.
> Such a dump could then be used to analyze whether we have some kind of
> memory leak or not.
>
> -XX:ErrorFile=./hs_err_pid<pid>.log     If an error occurs, save the
> error data to this file. (Introduced in 6.)
>
> -XX:HeapDumpPath=./java_pid<pid>.hprof  Path to directory or filename
> for heap dump. Manageable. (Introduced in 1.4.2 update 12, 5.0 update
> 7.)
>
> -XX:-HeapDumpOnOutOfMemoryError         Dump heap to file when
> java.lang.OutOfMemoryError is thrown. Manageable. (Introduced in 1.4.2
> update 12, 5.0 update 7.)
>
> I rather suspect that we are loading too many classes at once (maybe
> some declared static?). See...
>
> Java JVM GC, PermGen, and Memory Options:
> http://www.brokenbuild.com/blog/2006/08/04/java-jvm-gc-permgen-and-memory-options/
>
> The max PermGen size can be set like this: java -XX:PermSize=64m
> -XX:MaxPermSize=512m
>
> NOTE: This is not a heap size issue it's a perm size issue and we just
> tried to tweak the heap size AFAIK.
>
> Cheers
> Daniel
>
> Btw,
>