Ok, this leak can be avoided by updating rapidly changing components with jQuery before upgrading to Wicket 6,
-Heikki -----Original Message----- From: Heikki Uotinen [mailto:heikki.uoti...@syncrontech.com] Sent: 3. huhtikuuta 2012 16:17 To: users@wicket.apache.org Subject: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5) Hi, it seems that IE9 leaks memory heavily when updating components with Ajax in IE9 document mode. There is no leak after setting document to IE8 mode <meta http-equiv="X-UA-Compatible" content="IE=8"/> Any ideas to resolve this without forcing IE8 mode ? There have been past issues, but found no current issue related to this, quick start code is very simple, Opera, Firefox, Chrome work fine. public HomePage(final PageParameters parameters) { Label testDiv = new Label("testDiv", new PropertyModel(this, "data")); testDiv.setOutputMarkupId(true); add(testDiv); AjaxSelfUpdatingTimerBehavior timer = new AjaxSelfUpdatingTimerBehavior(Duration.milliseconds(200)); testDiv.add(timer); } public String getData() { Date now = new Date(); return now.toString(); } <html> <head> <!-- No leak if this is set <meta http-equiv="X-UA-Compatible" content="IE=8"/> --> </head> <body> <div wicket:id="testDiv"></div> </body> </html> -Heikki --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
