[jira] [Comment Edited] (WICKET-6085) AjaxTimerBehavior with failure handler cause memory leak in browser

["Sven Meier (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134219#comment-15134219 ] 

Sven Meier edited comment on WICKET-6085 at 2/5/16 5:58 PM:
------------------------------------------------------------

I've checked with Chrome's memory tool and it seems any function in the ajaxAttributes leaks a reference to the <evaluate> node from the response.

Moving eval(script) out of scope fixes this:

{code}
	safeEval = function(script) {
		return eval(script);
	};
{code}

I'll investigate further.


was (Author: svenmeier):
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)