You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2010/08/31 02:15:54 UTC

[jira] Commented: (WICKET-2850) Wicket DateTimeField / DatePicker creates a memory leak on the browser when rerenderd using ajax requests

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

Hudson commented on WICKET-2850:
--------------------------------

Integrated in Apache Wicket 1.4.x #133 (See [https://hudson.apache.org/hudson/job/Apache%20Wicket%201.4.x/133/])
    WICKET-2850


> Wicket DateTimeField / DatePicker creates a memory leak on the browser when rerenderd using ajax requests
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-2850
>                 URL: https://issues.apache.org/jira/browse/WICKET-2850
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-datetime
>         Environment: Firefox 3.6, Internet Explorer 8, Opera 9.10
>            Reporter: Andre L
>            Assignee: Igor Vaynberg
>            Priority: Minor
>             Fix For: 1.4.11, 1.5-M2
>
>         Attachments: Dummy.html, Dummy.java, WICKET-2850.patch
>
>
> When a wicket DateTimeField is repeatedly added to a page using  AjaxRequestTarget#addComponent(..) it creates a memory leak on the browser. This will eventually cause memory starvation
> on the client machine.
> The error can be reproduced by using a DateTimeField component that updates itself using the AjaxSelfUpdatingTimeBehavior. 
> DateTimeField field= new DateTimeField("field", new Model<Date>(new Date()));
> field.add(new AjaxSelfUpdatingTimerBehavior(Duration.seconds(0.5)));
> add(field);
> Running this for just an hour or so clearly shows that the browsers do not free up resources. The problem seems to be related to how wicket-date.js reinitializes a new Yahoo Yui Calendar widget using the same element id on each rerendering. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.