Hi, I tested against apache-wicket-6.0.0-beta1 with that simple example in the first mail.
Application still leaked memory on IE9 document mode, same behavior as with 1.5.5. Confirmed that it is using jQuery: <script type="text/javascript" src="../resource/org.apache.wicket.resource.JQueryResourceReference/jquery/jquery-ver-1334139767559.js"></script> <script type="text/javascript" src="../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/res/js/wicket-event-jquery-ver-1334139767559.js"></script> <script type="text/javascript" src="../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/res/js/wicket-ajax-jquery-ver-1334139767559.js"></script> Suggestions ? -----Original Message----- From: Chris Colman [mailto:[email protected]] Sent: 11. huhtikuuta 2012 11:47 To: [email protected] Subject: RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5) >> how exactly did you solve it with jQuery ? > >Since this leak seems to be caused by wicket-ajax calls then solution would >be bypassing >those, this would be the last resort. Wicket 6 uses jQuery for its AJAX backhauling. I wonder if, therefore, if your app were ported to Wicket 6 if the IE9 problem goes away. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
