[
https://issues.apache.org/jira/browse/WICKET-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sven Meier resolved WICKET-6085.
--------------------------------
Resolution: Fixed
By evaluating the expression in the global scope, the result can of course no
longer access any local variables:
- the resulting function could no longer be assigned to 'f', I fixed this by
returning the function from the evaluated expression
- the JS evaluation can no longer access the 'context', so I removed the
counter increment from twoEvaluationsWithIdentifier.xml - the qunit assertions
should be sufficient to ensure the test outcome
> 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
> Fix For: 7.3.0, 8.0.0-M1, 6.22.0
>
> 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)
