Ok, it seems that time takes care of this problem and leak is not wicket-ajax problem:
Tests with IE 10 (consumer preview) shows no leaking, gc seems to work and browser refresh clears the memory. There were no leaking with Opera, Firefox and Chrome. Furthermore previous JS debugging did not show that anything was piling in dom, so it must be IE9 inner problem. Only leaking is this IE9 in IE9 document mode, can't see any point filing a ticket. Anyway quickstart is available at http://uploading.com/files/51fc2bcb/ie9memory.zip/ Easy way to check Process Explorer -> "select iexplore.exe"-> Properties..-> Performance Graph -> Private bytes -----Original Message----- From: Heikki Uotinen [mailto:heikki.uoti...@syncrontech.com] Sent: 11. huhtikuuta 2012 14:38 To: users@wicket.apache.org Subject: RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5) Hi, 1) Process Explorer and IE developer tools 2) ok -----Original Message----- From: Martin Grigorov [mailto:mgrigo...@apache.org] Sent: 11. huhtikuuta 2012 14:14 To: users@wicket.apache.org Subject: Re: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5) Hi, From your mails I still don't understand how exactly you measure the memory consumption. You have two options: 1) google for "javascript memory leak". You can add "Internet explorer" in the search term too I'm not sure whether IE has tools to deal with that but you can use and see whether it helps somehow 2) create a ticket in Wicket Jira with a quickstart and detailed description how to reproduce and how to measure and let someone else to debug it for you. On Wed, Apr 11, 2012 at 1:50 PM, Heikki Uotinen <heikki.uoti...@syncrontech.com> wrote: > 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/jq > uery/jquery-ver-1334139767559.js"></script> > > <script type="text/javascript" > src="../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/re > s/js/wicket-event-jquery-ver-1334139767559.js"></script> > > <script type="text/javascript" > src="../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/re > s/js/wicket-ajax-jquery-ver-1334139767559.js"></script> > > Suggestions ? > > > -----Original Message----- > From: Chris Colman [mailto:chr...@stepaheadsoftware.com] > Sent: 11. huhtikuuta 2012 11:47 > To: users@wicket.apache.org > 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: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
