-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
linux
After an upgrade to version 1.546 Jenkins became very unstable crashing 2-4 times per day. From what I can tell it is because of missing junitResult.xml files when jenkins tries to load the test trend.
Attached is a snippet from the log where you can see the FileNotFoundException for the junitResult.xml file followed by a StackOverFlow error and then an out of memory error.
Also attached is a screen shot from a heap analysis showing that the request handler thread building the test trend is holding a considerable amount of the heap. Please note that this particular heap analysis is from a different crash than the log snippet. I did not analyze the heap on the crash shown in the log, but I am sure it would show the test trend for the same job that throw the StackOverFlow.
[JENKINS-21422] Jenkins crashing due to out of memory when rebuilding jobs
Description |
Original:
After an upgrade to version 1.546 Jenkins became very unstable crashing 2-4 times per day. From what I can tell it is because of missing junitResult.xml files when jenkins tries to load the test trend. Attached is a snippet from the log where you can see the FileNotFoundException for the junitResult.xml file followed by a StackOverFlow error and then an out of memory error. Also attached is a screen shot from the heap analysis showing that the request handler thread building the test trend is holding a considerable amount of the heap. |
New:
After an upgrade to version 1.546 Jenkins became very unstable crashing 2-4 times per day. From what I can tell it is because of missing junitResult.xml files when jenkins tries to load the test trend. Attached is a snippet from the log where you can see the FileNotFoundException for the junitResult.xml file followed by a StackOverFlow error and then an out of memory error. Also attached is a screen shot from a heap analysis showing that the request handler thread building the test trend is holding a considerable amount of the heap. Please note that this particular heap analysis is from a different crash than the log snippet. I did not analyze the heap on the crash shown in the log, but I am sure it would show the test trend for the same job that throw the StackOverFlow. |
Attachment | New: heap-dump-capture.PNG [ 25026 ] |
Summary | Original: Jenkins crashing with StackOverFlow error | New: Jenkins crashing due to out of memory |
Component/s | New: build-pipeline [ 15962 ] | |
Affects Version/s | New: current [ 10162 ] |
Summary | Original: Jenkins crashing due to out of memory | New: Jenkins crashing due to out of memory when rebuilding jobs |
Attached is a different screen shot from the heap dump analysis that provides a little more context. The heap dump is 7GB making it difficult to share.