The title of this bug was "Memory leak and long operation pauses".

We are confident that we found the reason for the sluggishness and had nothing to do with Jenkins. i've updated the title accordingly.

We do still have the problem of the memory leak.

Change By: Mario Rincon (05/Jan/15 11:03 PM)
Summary: Memory leak  and long operation pauses
Description: From the moment Jenkins is started up, it begins consuming RAM slowly. After several hours (~18h), the memory is totally consumed.
Additionally, for most GUI activities Jenkins is very slow. Listing the installed plugins, for example, takes several (+5) minutes. Showing a view  simple never happens; it keeps loading the page forever.

Other two Java processes are running on this machine.

We have 23 slaves. 9 of them are in offline status. We have a build queue of ~30 jobs always; some of these jobs don't go up because their assigned hosts are offline. I don't know if this matters.


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/d/optout.

Reply via email to