![]() |
|
|
|
|
|
|
Change By:
|
Uwe Stuehler
(27/Feb/13 1:39 PM)
|
|
Description:
|
(This issue was likely also reported on [Google Code|http://code.google.com/p/build-pipeline-plugin/issues/detail?id=143] by someone else but never answered.)
We're suffering from a severe memory leak that seems to be coming from the Build Pipeline plugin, growing with each HTTP request for the build pipeline view.
*Analysis*
!usedMemory.png|thumbnail,align=right!
We took a heap dump after just one work day of run-time and ran jhat on it. The graph shows memory usage growing almost linearly over the course of a day and the heap analysis shows an unusually high number of instances of the class {{au.com.centrumsystems.hudson.plugin.buildpipeline.BuildForm}}.
{noformat}
Instance Counts for All Classes (excluding platform)
806069 instances of class org.kohsuke.stapler.bind.BoundObjectTable$1
800273 instances of class au.com.centrumsystems.hudson.plugin.buildpipeline.BuildForm
800273 instances of class au.com.centrumsystems.hudson.plugin.buildpipeline.PipelineBuild
51265 instances of class hudson.util.CopyOnWriteList
31526 instances of class hudson.util.DescribableList
30784 instances of class [Lorg.apache.commons.jexl.parser.Node;
24643 instances of class jenkins.model.lazy.BuildReference
24228 instances of class net.bull.javamelody.CounterRequest
22565 instances of class com.thoughtworks.xstream.core.util.ConcurrentWeakHashMap$HashEntry
22565 instances of class com.thoughtworks.xstream.core.util.ConcurrentWeakHashMap$WeakKeyReference
18441 instances of class hudson.model.View$PropertyList
{noformat}
*Workaround*
We are restarting Jenkins every night, which causes other problems.
*
In [issue 143|http://code.google.com/p/build-pipeline-plugin/issues/detail?id=143] on Google Code, the reporter also mentioned that they downgraded the plugin to version "1.2.3".
* We were restarting Jenkins every night, which caused other problems.
* For now, we're able to free up memory by identifying the session that keeps refreshing the pipeline view and killing that session.
|
|
|
|
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
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
Describe a new workaround: killing the session that contains the leak.