[
https://issues.apache.org/jira/browse/WICKET-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134219#comment-15134219
]
Sven Meier commented on WICKET-6085:
------------------------------------
I've checked with Chrome's memory tools and it seems that this problem is not
directly related to a failure handler. It's just that with Ajax attributes
getting 'larger' the leak becomes more apparent.
> 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
> 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)
