You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2014/04/23 15:24:15 UTC
[jira] [Commented] (WICKET-5570) Rescheduling the same ajax timer
behavior causes memory leak in the browser
[ https://issues.apache.org/jira/browse/WICKET-5570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13978180#comment-13978180 ]
Martin Grigorov commented on WICKET-5570:
-----------------------------------------
Decebal, please test with 6.16.0-SNAPSHOT to verify the fix. Thanks!
> Rescheduling the same ajax timer behavior causes memory leak in the browser
> ---------------------------------------------------------------------------
>
> Key: WICKET-5570
> URL: https://issues.apache.org/jira/browse/WICKET-5570
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.14.0
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Fix For: 7.0.0, 6.16.0
>
> Attachments: wicket-push-test.zip
>
>
> AbstractAjaxTimerBehavior uses JavaScript setTimeout() function to do its job. It has a #stop() method that clears the timeout but if the timeout is re-scheduled without being cleared a memory leak is observed in the browser.
--
This message was sent by Atlassian JIRA
(v6.2#6252)