[JIRA] (JENKINS-14473) Jenkins server memory leak

Anoop Karollil created JENKINS-14473

Jenkins server memory leak

Issue Type:	Bug
Affects Versions:	current
Assignee:	Unassigned
Attachments:	JavaMelody__build_7_17_12.pdf, usedMemory-month.png, usedMemory.png
Components:	core
Created:	17/Jul/12 8:52 PM
Description:	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.
Environment:	Ubuntu 7.10 running on 32bit dual core. Jenkins with Winstone.
Project:	Jenkins
Labels:	jenkins memory-leak memory winstone
Priority:	Major
Reporter:	Anoop Karollil

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

Anoop Karollil updated JENKINS-14473

Jenkins server memory leak

Change By:

Anoop Karollil (17/Jul/12 8:54 PM)

Description:

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.

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

Anoop Karollil updated JENKINS-14473

Jenkins server memory leak

Change By:	Anoop Karollil (27/Jul/12 7:00 PM)
Attachment:	heapdump_Leak_Suspects.zip
Attachment:	heapdump_Top_Components.zip
Attachment:	heapdump_Top_Consumers.zip
Attachment:	heapdump_top_consumers_eclipse_memory_analyser.pdf

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

Anoop Karollil commented on JENKINS-14473

Jenkins server memory leak

Did some analysis using Eclipse's Memory Analyzer Tool with the heap dump attached. Report zip files and a PDF attached.

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

Anoop Karollil updated JENKINS-14473

Jenkins server memory leak

Change By:	Anoop Karollil (27/Jul/12 7:01 PM)
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)

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

Liya Katz commented on JENKINS-14473

Jenkins server memory leak

Upgrading to 1.492 (from 1.473) has solved this problem for us.

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

Anoop Karollil commented on JENKINS-14473

Jenkins server memory leak

Thanks Liya. I did see a few weeks ago (memory usage crept up to 5gigs of RAM), but things have been okay the past week with 1.491 - upgraded to 1.492 anyway. Hopefully this has been resolved - I will close this bug once I am sure.

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