[
https://issues.jenkins-ci.org/browse/JENKINS-13109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161153#comment-161153
]
Tim Drury commented on JENKINS-13109:
-------------------------------------
I noticed the same error today on 1.450 w/ perforce plugin 1.3.7. In my case,
it isn't caused by huge changelogs - at least that I can tell. We don't have
huge changelogs. We do have 2 slaves and all polling is done on the master.
Here is the stack trace:
Apr 1, 2012 7:48:48 PM hudson.triggers.SCMTrigger$Runner runPolling
SEVERE: Failed to record SCM polling
java.lang.OutOfMemoryError: Java heap space
at
hudson.remoting.FastPipedInputStream.<init>(FastPipedInputStream.java:78)
at
hudson.remoting.FastPipedInputStream.<init>(FastPipedInputStream.java:66)
at
hudson.plugins.perforce.HudsonP4RemoteExecutor.exec(HudsonP4RemoteExecutor.java:97)
at
com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:321)
at
com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292)
at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:54)
at
hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1208)
at
hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:903)
at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356)
at hudson.scm.SCM.poll(SCM.java:373)
at hudson.model.AbstractProject.poll(AbstractProject.java:1323)
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:662)
We do keep Jenkins running without period reboots so I'm thinking there may be
a memory leak somewhere as well. If anyone can give me hints how to get more
information, I'll try to provide it.
-tim
> 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
