[JIRA] [core] (JENKINS-25081) Memory leak in ProgressiveRendering

[jgl...@cloudbees.com (JIRA)]

Jesse Glick created JENKINS-25081 Memory leak in ProgressiveRendering Issue Type: Bug Assignee: Unassigned Components: core Created: 09/Oct/14 9:35 PM Description: A special case of JENKINS-16341 is that you are using ProgressiveRendering (as opposed to, say, l:renderOnDemand or st:bind). This is fixable in principle because we know when the rendering thread is finished. The easy case is that the page is fully rendered, in which case news is called at the end and we can use BoundObjectTable.releaseMe. The harder case is that the user navigates away from this page (or otherwise stops _javascript_ rendering); then we know when we are done, but releaseMe does not work, and there is no API to find the Bound to call release on. Project: Jenkins Labels: memory-leak performance stapler lts-candidate Priority: Major Reporter: Jesse Glick

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.