Also users of ProgressiveRendering would be affected. Though this class implements its own ping-based timeout, returning "canceled" from news(), that does not also call Bound.release. The only fix for that, other than a general fix of this issue, would be to make ProgressiveRendering implement WithWellKnownURL, adding ongoing renders to a map keyed by random UUID and deleting them after sending back a cancel status.

Code changed in jenkins
User: Jesse Glick
Path:
changelog.html
core/src/main/java/hudson/widgets/RenderOnDemandClosure.java
http://jenkins-ci.org/commit/jenkins/47d6811666d5eb20bc491ea6ad4bda8f54f83be4
Log:
JENKINS-16341 Amelioration of memory leak by at least interning some heavily redundant strings.
(cherry picked from commit 08efdf5d3ab962cfd4c4c489266592fe1db7df8e)

Conflicts:
changelog.html
core/src/main/java/hudson/widgets/RenderOnDemandClosure.java

Code changed in jenkins
User: Jesse Glick
Path:
test/src/main/java/org/jvnet/hudson/test/MemoryAssert.java
test/src/test/java/lib/layout/RenderOnDemandTest.java
http://jenkins-ci.org/commit/jenkins/5fe628076b6ee03f57bfa0767c6d0775aeafac1e
Log:
JENKINS-16341 INSANE testing shows that a RenderOnDemandClosure binding adds about 380k, with or wothout 08efdf5.(cherry picked from commit f178f0cef4bf86c5fb4cf4a2c40afce4c2b43410)

Conflicts:
test/src/main/java/org/jvnet/hudson/test/MemoryAssert.java
test/src/test/java/lib/layout/RenderOnDemandTest.java

There is BoundObjectTable.releaseMe but it does not seem to be called by anything. Nor does its implementation make sense: you would expect it to be static and actually use the BoundObjectTable instance found in the Ancestor.

Code changed in jenkins
User: Jesse Glick
Path:
test/src/main/java/org/jvnet/hudson/test/MemoryAssert.java
http://jenkins-ci.org/commit/jenkins-test-harness/5eaf5f7459cf0bda87d9023f4c3f6080a073cbf6
Log:
JENKINS-16341 INSANE testing shows that a RenderOnDemandClosure binding adds about 380k, with or wothout 08efdf5.
Originally-Committed-As: f178f0cef4bf86c5fb4cf4a2c40afce4c2b43410