-
Bug
-
Resolution: Duplicate
-
Blocker
-
ubuntu 13.04
java 1.7.0_51
apache2 2.2.22
Between Jenkins version 1.558 and 1.561 a serious regression in the heap memory management of Jenkins occurred.
$ top
shows that the memory consumption of 1.561 is steadily increasing (building only on slaves).
Jenkins first loses connection to one or more slaves it is building on (out of heap exception) and finally it is not reachable over its URL anymore.
W/ 1.558 memory usage stays within limits.
[JENKINS-22815] Jenkins runs out of Heap Memory
Could you provide a heap dump statistics?
The issue could be related to JENKINS-22170, but version ranges differ
Eric Schwarz
added a comment - Well, I gave the Java VM 6 out of 8 GB of memory (configured in /etc/default/jenkins).
It is eaten up in minutes.
The Jenkins master just controls OSX, Linux and a Windows slave.
It copies the artifacts back to the master.
A heap dump can't be provided at the moment since I downgraded to version 1.558 again since we are about to ship our new camera and managing all our builds including those for our FPGAs (~12h each) over Jenkins.
Maybe when the product is shipped I could give it a chance.
Maybe Ed Meagher could provide one?!
Eric Schwarz
added a comment - Well, I gave the Java VM 6 out of 8 GB of memory (configured in /etc/default/jenkins).
It is eaten up in minutes.
The Jenkins master just controls OSX, Linux and a Windows slave.
It copies the artifacts back to the master.
A heap dump can't be provided at the moment since I downgraded to version 1.558 again since we are about to ship our new camera and managing all our builds including those for our FPGAs (~12h each) over Jenkins.
Maybe when the product is shipped I could give it a chance.
Maybe Ed Meagher could provide one?! 
Robin Kaluzny
added a comment - Hi,
I have the same problem under debian squeeze, java 1.7.0_55-b13 and jenkins 1.562. I have a heapdump too, but the dump is to big for attachment (ca 850 mb unzipped, 430 mb zipped).
Suggestion?
Robin Kaluzny
added a comment - Hi,
I have the same problem under debian squeeze, java 1.7.0_55-b13 and jenkins 1.562. I have a heapdump too, but the dump is to big for attachment (ca 850 mb unzipped, 430 mb zipped).
Suggestion? Robin Kaluzny
added a comment - In my case I archive debian packages(32, total size ca 330 mb) and logfiles(29, total size ca 1 mb) of compiling and building the packages. Now I don't archive the debian packages anymore and it seems's to be more stable.
Robin Kaluzny
added a comment - In my case I archive debian packages(32, total size ca 330 mb) and logfiles(29, total size ca 1 mb) of compiling and building the packages. Now I don't archive the debian packages anymore and it seems's to be more stable. Given the version range and description, this is likely JENKINS-22734, which affects 1.560-1.562.
miroy roy
added a comment - I am seeing the exact same issue after upgrading Jenkins to 1.561 version. Memory usage continues to grow and eventually gives Java Memory Heap issue. One of the nodes keep on going offline. This particular node uses Archive Artifacts plugin. Any solution other than downgrading Jenkins?
miroy roy
added a comment - I am seeing the exact same issue after upgrading Jenkins to 1.561 version. Memory usage continues to grow and eventually gives Java Memory Heap issue. One of the nodes keep on going offline. This particular node uses Archive Artifacts plugin. Any solution other than downgrading Jenkins? 
I'm seeing the same thing with 1.561 and java "jdk1.7.0_21"