-
Bug
-
Resolution: Unresolved
-
Major
We have a Jenkins instance that is heavily utilizing Build Pipeline plugin. On a weekly or bi-weekly basis, Jenkins runs out of memory. Taking a heapdump and analyzing it for leak suspects indicated that build pipeline plugin is a culprit. Below are tables from leak suspects report taken from the heapdump:
| Label | Number of Objects | Used Heap Size | Retained Heap Size |
|---|---|---|---|
| au.com.centrumsystems.hudson.plugin.buildpipeline.BuildForm | 7,126,445 | 285,057,800 | 1,881,469,128 |
| – java.util.HashMap$Entry | 6,535,640 | 209,140,480 | 1,669,522,544 |
| Total: 2 entries | 13,662,085 | 494,198,280 | 3,550,991,672 |
Given the fact that the JVM runs on 8G of heapspace, total size of objects related to build pipeline plugin occupies nearly half of that. Big difference between retained and used heap sizes shows that heap space is not being freed fast enough.
I'm also attaching a screenshot of heap dump histogram for a more complete picture.
Version of Jenkins: 1.588
Version of build pipeline plugin: 1.4.5
- is duplicated by
-
-
- Open
-
