![]() |
|
|
|
|
Change By:
|
Ronen Peleg
(04/Dec/13 6:36 AM)
|
|
Labels:
|
1.509.4
1.509.4LTS 1.532.1 1.532.1LTS
Jenkins LTS
|
|
Description:
|
After Jenkins upgraded to LTS 1.509.4 from LTS 1.509.3 I notice that over time (24 hours) Jenkins becomes very slowly.
It turns out that Jenkins (under Jetty service) slowly "eats" the server memory. It's takes about 24 hours to take all the memory allocated to Jenkins (42GB). See the snapshots with examples...
TEST #1 on LTS 1.509.4:
1. Machine with Jetty up after restart
2. Jenkins Used - After one Hour: 22GB
3. Jenkins Used - After 12 Hours: 27GB
4. Jenkins Used - After 20 Hours: 35GB -> Memory leaks between 10:00-10:20 as you can see after GC it's still think Java in-use and fail to cleanup the all memory as it should be.
5. Jenkins Used - After 23 Hours: 39GB -> Very slow response and Heap is almost 100%
TEST #2 on LTS 1.509.4:
I tried to do manual GC, Doesn't help!
(see attach file: "Monitor_Memory_Over_Time_Manual_GC")
TEST #3 on LTS 1.509.3:
Unfortunately I downgrade to LTS 1.509.3 because
of the
memory leak
,
for me it's a blocker issue!
On
BTW: In
version LTS 1.509.3 Jenkins works stable without any memory leaks... (see attach file: "Good_GC_A1.509.3")
but with one big unsolved problem, I can't rename jobs (deadlock)!
TEST #4 with LTS 1
.
532.1:
Same issue! Jenkins stuck with 100% memory usage after only 12 hours!
Thanks
Thank You
,
Ronen.
|
|
|
|
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
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
