[
https://issues.jenkins-ci.org/browse/JENKINS-13109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160687#comment-160687
]
lestin commented on JENKINS-13109:
----------------------------------
We seem to have the same problem as well. Our files are not that big and it
start to halt the webpage around log part 1560.
The biggest impact was, the webpage was not responsive and the only way we can
do is kill the java process. --- Is there a better way?
Thanks.
=========================
Mar 23, 2012 2:33:15 PM hudson.plugins.logparser.LogParserReader readLogPart
INFO: Done reading log part 1560
Mar 23, 2012 2:33:15 PM hudson.plugins.logparser.LogParserThread getLineStatuses
INFO: LogParserThread: Start parsing log part 1560
Mar 23, 2012 2:33:15 PM hudson.triggers.SCMTrigger$Runner runPolling
SEVERE: Failed to record SCM polling
java.lang.OutOfMemoryError: GC overhead limit exceeded
at java.io.BufferedReader.<init>(BufferedReader.java:80)
at java.io.BufferedReader.<init>(BufferedReader.java:91)
at
hudson.plugins.perforce.HudsonP4DefaultExecutor.getReader(HudsonP4DefaultExecutor.java:123)
at
com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:322)
at
com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292)
at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61)
at
hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325)
at
hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019)
at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356)
at hudson.scm.SCM.poll(SCM.java:373)
at hudson.model.AbstractProject.poll(AbstractProject.java:1340)
at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420)
at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449)
at
hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Mar 23, 2012 2:33:22 PM hudson.plugins.logparser.LogParserThread getLineStatuses
INFO: LogParserThread: Done parsing log part 1553
Mar 23, 2012 2:33:15 PM hudson.plugins.logparser.LogParserReader readLogPart
INFO: Start reading log part 1561 in thread #104
====================================
> 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
