[JIRA] (JENKINS-13617) 64-bit java.lang.OutOfMemoryError: PermGen space

Thu, 03 Jan 2013 08:51:58 -0800

Heap dump looks better than before. This time it blew up at

"Pipe writer thread: Jenkins-win7" prio=5 tid=16893 RUNNABLE
at java.lang.OutOfMemoryError.<init>(OutOfMemoryError.java:25)
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
at java.lang.Class.getConstructor0(Class.java:2699)
at java.lang.Class.newInstance0(Class.java:326)
Local Variable: java.lang.Class[]#7844
at java.lang.Class.newInstance(Class.java:308)
Local Variable: class sun.reflect.GeneratedSerializationConstructorAccessor6164
at sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:381)
Local Variable: sun.reflect.MethodAccessorGenerator$1#1
at java.security.AccessController.doPrivileged(Native Method)
at sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:377)
Local Variable: java.lang.String#60850
Local Variable: sun.reflect.ByteVectorImpl#1
Local Variable: java.lang.Class#9
..

winstone.classLoader.WebappClassLoader seems to be holding on to quite a lot of classes, but this might as well be normal behaviour. What are your current memory settings for the JVM? If they have been omitted please try restarting the JVM with the following flags "-XX:MaxPermSize=256m -Xmx768m -XX:+CMSClassUnloadingEnabled -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/jenkins/memory.dump". To rule out memory leaks with the Winstone container you could also try running Jenkins on Tomcat to see if it helps or not.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to