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
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
@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
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
/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/res/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
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
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
: 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 heikki.uoti...@syncrontech.com
wrote:
Ok, this leak can
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
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
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
11 matches
Mail list logo