• Type: Bug
• Resolution: Fixed
• Priority: Major
• Component/s: core
• Labels:

  • jenkins
  • memory
  • memory-leak
  • winstone
• Environment:

  Ubuntu 7.10 running on 32bit dual core. Jenkins with Winstone. Java version "1.6.0_03", Java(TM) SE Runtime Environment (build 1.6.0_03-b05), Java HotSpot(TM) Server VM (build 1.6.0_03-b05, mixed mode)

1. JavaMelody__build_7_17_12.pdf

   435 kB

   2012-07-17 20:52

2. 

   usedMemory-month.png

   28 kB

   2012-07-17 20:52

3. 

   usedMemory.png

   25 kB

   2012-07-17 20:52

4. heapdump_Leak_Suspects.zip

   106 kB

   2012-07-27 19:00

5. heapdump_Top_Components.zip

   224 kB

   2012-07-27 19:00

6. heapdump_Top_Consumers.zip

   70 kB

   2012-07-27 19:00

7. heapdump_top_consumers_eclipse_memory_analyser.pdf

   305 kB

   2012-07-27 19:00

[JENKINS-14473] Jenkins server memory leak

Anoop Karollil created issue - 2012-07-17 20:52

Anoop Karollil made changes - 2012-07-17 20:54

Description

Original: I am not sure I have filed this under the right component. We are seeing steady gradual increases in memory usage for our Jenkins (see attached graphs). It does not result in the OutOfMemoryError but usually results in Jenkins utilizing 100% of CPU (one core in our case). Attached is a memory histogram report and heap dump generated using the Monitoring Plugin. This happens consistently and our work around for now is to restart Jenkins each time it gets too bloated. If this doesn't get fixed, we will have to stop using Winstone and use Jetty - because there seems to be a connection between the servlet(?) wrapper (winstone/jetty) and the leak - pretty sure we did not see this when using Jetty.

New: I am not sure I have filed this under the right component. We are seeing steady gradual increases in memory usage for our Jenkins (see attached graphs). It does not result in the OutOfMemoryError but usually results in Jenkins utilizing 100% of CPU (one core in our case). Attached is a memory histogram report and the link include (see URL above) is to a heap dump generated using the Monitoring Plugin. This happens consistently and our work around for now is to restart Jenkins each time it gets too bloated. If this doesn't get fixed, we will have to stop using Winstone and use Jetty - because there seems to be a connection between the servlet(?) wrapper (winstone/jetty) and the leak - pretty sure we did not see this when using Jetty.

Anoop Karollil made changes - 2012-07-27 19:00

Attachment		New: heapdump_Leak_Suspects.zip [ 22229 ]
Attachment		New: heapdump_Top_Components.zip [ 22230 ]
Attachment		New: heapdump_Top_Consumers.zip [ 22231 ]
Attachment		New: heapdump_top_consumers_eclipse_memory_analyser.pdf [ 22232 ]

Anoop Karollil made changes - 2012-07-27 19:01

Environment

Original: Ubuntu 7.10 running on 32bit dual core. Jenkins with Winstone.

New: Ubuntu 7.10 running on 32bit dual core. Jenkins with Winstone. Java version "1.6.0_03", Java(TM) SE Runtime Environment (build 1.6.0_03-b05), Java HotSpot(TM) Server VM (build 1.6.0_03-b05, mixed mode)

Anoop Karollil made changes - 2013-12-11 19:26

Resolution		New: Fixed [ 1 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

R. Tyler Croy made changes - 2016-07-25 23:55

Workflow

Original: JNJira [ 145109 ]

New: JNJira + In-Review [ 191358 ]