[JIRA] (JENKINS-16341) Memory leak in createJavaScriptProxy

[k...@kohsuke.org (JIRA)]

Kohsuke Kawaguchi commented on JENKINS-16341 Memory leak in createJavaScriptProxy The other thing that helps is to make proxies have well-known URLs. If the fragment rendered on-demand do not depend on the request context (or if it can be recreated from future requests), then there won't be any need to keep session-scoped objects. Some of the core tags might very well fit with this, since they explicitly lists variables that get captured. But otherwise I agree that ping is the only way I can think of.

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