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

Tim Drury edited comment on JENKINS-13109 at 4/3/12 6:59 PM:
-------------------------------------------------------------

Ok, I'll move my stack trace to a new issue and I'll update with OOM Error info 
when/if it occurs again.  Thanks again, Rob.

Created this issue: https://issues.jenkins-ci.org/browse/JENKINS-13332
                
      was (Author: timdrury):
    Ok, I'll move my stack trace to a new issue and I'll update with OOM Error 
info when/if it occurs again.  Thanks again, Rob.
                  
> Huge changelogs eat all the Java memory
> ---------------------------------------
>
>                 Key: JENKINS-13109
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13109
>             Project: Jenkins
>          Issue Type: Bug
>          Components: perforce
>         Environment: Windows Server 2008 HPC Edition
> 64-bit JVM 1.6.0_29
> Running Jenkins service with "<arguments>-Xrs -Xmx2048m 
> -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar 
> "%BASE%\jenkins.war" --httpPort=8080</arguments>"
>            Reporter: Mikko Tapaninen
>
> With really huge changelists the p4 plugin can run out of java heap space. At 
> least it looks like the reason for memory problems would be huge 
> changelog.xml files. An example case:
> - a changelist with > 400000 files
> - results in a changelog.xml size > 110MB
> - Jenkins runs out of memory: {{java.lang.OutOfMemoryError: Java heap space}}
> Maybe there should be an option to limit the amount of files that p4 plugin 
> reads to from changelists?

--
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