[
https://issues.apache.org/jira/browse/WICKET-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135199#comment-15135199
]
Sven Meier commented on WICKET-6085:
------------------------------------
Actually it is even simpler to execute eval() in global scope, just call:
window.eval(script).
Here's a good discussion of all the options:
http://perfectionkills.com/global-eval-what-are-the-options/
I can't think of any reason why a script returned inside an Ajax call might
need access to the local scope in #processEvaluation().
> AjaxTimerBehavior with failure handler cause memory leak in browser
> -------------------------------------------------------------------
>
> Key: WICKET-6085
> URL: https://issues.apache.org/jira/browse/WICKET-6085
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.21.0, 7.1.0
> Reporter: Vlastimil
> Assignee: Sven Meier
> Attachments: ajax-memory-leak-quickstart.zip
>
>
> Please see the attached quickstart.
> Start the application and run memory profiler in browser. Memory consumption
> gets high very quickly.
> I've tried to find the cause, but I'm too lame in Javascript to analyse that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
