Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-25081

Memory leak in ProgressiveRendering


      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.

            jglick Jesse Glick
            jglick Jesse Glick
            0 Vote for this issue
            3 Start watching this issue