RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)
As expected KB2675157 fixed this IE9 issue, nice timing though. -Original Message- From: Heikki Uotinen [mailto:heikki.uoti...@syncrontech.com] Sent: 12. huhtikuuta 2012 10:18 To: users@wicket.apache.org Subject: RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5) 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 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: > > src="../resource/org.apache.wicket.resource.JQueryResourceReference/jq > uery/jquery-ver-1334139767559.js"> > > src="../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/re > s/js/wicket-event-jquery-ver-1334139767559.js"> > > src="../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/re > s/js/wicket-ajax-jquery-ver-1334139767559.js"> > > 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
RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)
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 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: > > src="../resource/org.apache.wicket.resource.JQueryResourceReference/jq > uery/jquery-ver-1334139767559.js"> > > src="../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/re > s/js/wicket-event-jquery-ver-1334139767559.js"> > > src="../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/re > s/js/wicket-ajax-jquery-ver-1334139767559.js"> > > 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
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 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: > > src="../resource/org.apache.wicket.resource.JQueryResourceReference/jq > uery/jquery-ver-1334139767559.js"> > > src="../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/re > s/js/wicket-event-jquery-ver-1334139767559.js"> > > src="../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/re > s/js/wicket-ajax-jquery-ver-1334139767559.js"> > > 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
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 https://developers.google.com/chrome-developer-tools/docs/heap-profiling 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 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: > > src="../resource/org.apache.wicket.resource.JQueryResourceReference/jquery/jquery-ver-1334139767559.js"> > > src="../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/res/js/wicket-event-jquery-ver-1334139767559.js"> > > src="../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/res/js/wicket-ajax-jquery-ver-1334139767559.js"> > > 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
RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)
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: 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
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
RE: 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. can anyone confirm if this is Wicket related issue ? Forcing IE8 document mode will cause some problems in the future. Our use case is process displays where data comes from automation or other systems and data is updated frequently and those monitoring displays are open 24/7. Large customers have their own standards for browsers and versions they are using. If there are 50 simple text divs on the screen, then updating those every 10 seconds browser window consumes memory 3Mb in a minute in IE9 document mode, refreshing browser does not release memory. Normally updates happens more irregular and updating all fields at once makes user experience less comfortable 'cause there are other actions connected to those fields (links, tooltips, graphics). > 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. -Original Message- From: Heikki Uotinen [mailto:heikki.uoti...@syncrontech.com] Sent: 5. huhtikuuta 2012 18:50 To: users@wicket.apache.org Subject: RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5) Hi, maybe there is some gc problem with closures in IE9 document mode. Simple test page leaks memory in IE9 mode even if first suspect Wicket.replaceOuterHtmlIE is commented out. Test with plain XMLHttpRequest does not leak memory in any case. This Wicket Ajax example also slowly grows if IE9 document mode is set manually but is not seemingly leaking in IE8 mode http://www.wicket-library.com/wicket-examples/ajax/world-clock -Original Message- From: Martin Grigorov [mailto:mgrigo...@apache.org] Sent: 4. huhtikuuta 2012 9:19 To: users@wicket.apache.org Subject: Re: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5) Hi, Can you share your findings ? What exactly you think caused the memory leak and how exactly did you solve it with jQuery ? On Wed, Apr 4, 2012 at 8:14 AM, Heikki Uotinen wrote: > 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 > > > > 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(); > } > > > > > > > > > > > -Heikki > > - > 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 B CB [ X ܚX KK[XZ[ \ \ ][ X ܚX P X ] \X K ܙ B ܈Y][ۘ[ [X[ K[XZ[ \ \ Z[ X ] \X K ܙ B
RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)
Hi, maybe there is some gc problem with closures in IE9 document mode. Simple test page leaks memory in IE9 mode even if first suspect Wicket.replaceOuterHtmlIE is commented out. Test with plain XMLHttpRequest does not leak memory in any case. This Wicket Ajax example also slowly grows if IE9 document mode is set manually but is not seemingly leaking in IE8 mode http://www.wicket-library.com/wicket-examples/ajax/world-clock -Original Message- From: Martin Grigorov [mailto:mgrigo...@apache.org] Sent: 4. huhtikuuta 2012 9:19 To: users@wicket.apache.org Subject: Re: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5) Hi, Can you share your findings ? What exactly you think caused the memory leak and how exactly did you solve it with jQuery ? On Wed, Apr 4, 2012 at 8:14 AM, Heikki Uotinen wrote: > 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 > > > > 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(); > } > > > > > > > > > > > -Heikki > > - > 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
Re: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)
Hi, Can you share your findings ? What exactly you think caused the memory leak and how exactly did you solve it with jQuery ? On Wed, Apr 4, 2012 at 8:14 AM, Heikki Uotinen wrote: > 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 > > > > 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(); > } > > > > > > > > > > > -Heikki > > - > 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
RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)
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 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(); } -Heikki - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org