|
||||||||
|
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-16341) Memory leak in creat... [email protected] (JIRA)
- [JIRA] (JENKINS-16341) Memory leak in ... [email protected] (JIRA)
- [JIRA] (JENKINS-16341) Memory leak in ... [email protected] (JIRA)
- [JIRA] (JENKINS-16341) Memory leak in ... [email protected] (JIRA)
- [JIRA] (JENKINS-16341) Memory leak in ... [email protected] (JIRA)
- [JIRA] (JENKINS-16341) Memory leak in ... [email protected] (JIRA)
- [JIRA] (JENKINS-16341) Memory leak in ... [email protected] (JIRA)
- [JIRA] (JENKINS-16341) Memory leak in ... [email protected] (JIRA)
- [JIRA] (JENKINS-16341) Memory leak in ... [email protected] (JIRA)
- [JIRA] (JENKINS-16341) Memory leak in ... [email protected] (JIRA)
- [JIRA] (JENKINS-16341) Memory leak in ... [email protected] (JIRA)
- [JIRA] (JENKINS-16341) Memory leak in ... [email protected] (JIRA)

In Jenkins Enterprise, merely opening the config page for a newly created freestyle job results in >100 RenderOnDemandClosure instances being bound, none of which are ever released.