[ 
https://issues.jenkins-ci.org/browse/JENKINS-13827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163371#comment-163371
 ] 

Ed Palazzo commented on JENKINS-13827:
--------------------------------------

We continue to have this problem with OutOfMemory Exceptions. It happened again 
last night, which is about right... every one to two weeks.

Has anyone had a chance to look at the heap dump?

Thanks in advance.

-ed-
                
> Getting OutOfMemoryError after Jenkins has been running for several days
> ------------------------------------------------------------------------
>
>                 Key: JENKINS-13827
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13827
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>         Environment: Jenkins 1.458
> Red Hat Enterprise Linux ES release 4 (Nahant Update 4) 
> 32-bit hardware and OS
> java 1.6.0_17
> perforce plugin 1.3.8
> 8 virtual CPUs
> 16 GB total available memory on the system
>            Reporter: Ed Palazzo
>
> After running from anywhere from one to two weeks, Jenkins will appear to be 
> frozen. Examination of the logs shows the following error:
>  java.lang.OutOfMemoryError: GC overhead limit exceeded
> I've done numerous stack dumps, and it is fairly inconsistent as to what is 
> happening when the error occurs. This last time I did a heap dump per the 
> instructions on this page: 
> https://wiki.jenkins-ci.org/display/JENKINS/I%27m+getting+OutOfMemoryError
> The heap is available for download via FTP here:  
> ftp://Jenkins:maqla...@kpsg.kofax.com/heap.bin.gz
> It's about 300M compressed (~1.6GB uncompressed). I had a hard time running 
> jhat against the heap -- maybe you'll have more luck.
> I should let you know that I have 565 jobs (all modules of different 
> branches) configured on this system. I have one slave running builds, with 
> another two machines on the way.
> Let me know what else I can provide to help debug.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to