-
Bug
-
Resolution: Fixed
-
Major
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.
- is blocking
-
JENKINS-16341 Memory leak in createJavaScriptProxy
-
- Open
-
-
JENKINS-25075 Weather column should render asynchronously
-
- Open
-
Code changed in jenkins
User: Jesse Glick
Path:
changelog.html
core/src/main/java/jenkins/util/ProgressiveRendering.java
core/src/main/resources/lib/layout/progressiveRendering.jelly
core/src/main/resources/lib/layout/progressiveRendering/progressiveRendering.js
http://jenkins-ci.org/commit/jenkins/aac8c239721ed52caacbff389a29d5db2c1e3a00
Log:
[FIXED JENKINS-25081] Memory leak in BoundObjectTable when ProgressiveRendering is used.