|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-16023) Lazy loading causes... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading c... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading c... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading c... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading c... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading c... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading c... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading c... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading c... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading c... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading c... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading c... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading c... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading c... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading c... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading c... [email protected] (JIRA)

Purging the build history has helped somewhat, however when Jenkins runs a job which chews up a lot of memory it must trigger full GC which causes Jenkins to reload all the build history again causing massive delays loading dashboard.