|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I am on 1.539. I too have major memory usage. It quickly climbs to 5.5GB (the max I set it for) just after the service is started, without loading the UI. I tried disabling most plugins I thought were culprits.
Some plugins that I used (Fitnesse), I even temporarily disabled some calls like Parent.getBuilds(), which might have been the cause of loading all build history in memory. But there must be more places that load all the build history, instead of properly using the Lazy Loading of builds.
Any ideas?
Using Windows 7 with Java 64bit (7.45) with "Xrs -Xmx5g -XX:MaxPermSize=1g -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "%BASE%\jenkins.war". (mainly as a test, definitely didn't expect all the 5GB of memory to quickly be used).
Plugins:
Name ↓ Version
analysis-core 1.54
ant 1.2
build-timeout 1.12
clone-workspace-scm 0.6
credentials 1.9.1
cygpath 1.5
dry 2.37
email-ext 2.32
fitnesse 1.9-SNAPSHOT (private-11/14/2013 23:29-Sean)
greenballs 1.12
join 1.15
ldap 1.2
mailer 1.5
matrix-auth 1.0.2
maven-plugin 2
msbuild 1.21
pam-auth 1
parameterized-trigger 2.2
schedule-failed-builds 1.1
ssh-credentials 1.5.1
ssh-slaves 1.5
subversion 1.5
thinBackup 1.7.3
token-macro 1.8.1
violations 0.7.11
ws-cleanup 0.16
xunit 1.5