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

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.4.11, 1.5-M2.1
• Component/s: wicket-datetime
• Labels: ajax calendar yahoo
• Environment: Firefox 3.6, Internet Explorer 8, Opera 9.10
• Assignee: Igor Vaynberg
• Reporter: Andre L
• Created: 27/Apr/10 13:49
• Updated: 08/Feb/11 13:12
• Resolved: 30/Aug/10 23:52

Description

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.

Issue Links

• is blocked by: WICKET-3430 Wicket example ajax modal-window does not work with the "dialog with panel"