Ari Suutari wrote:
Hi,
Thanks for you response,
I changed the wicket-ajax.js to create only one instance of
XmlHttpRequest, and the memory leak in IE seemed to vanish.
So the problem is that creating XmlHttpRequest probably causes a
memory leak. Howewer, having only one instance of XmlHttpRequest
doesn't seem to be the best idea either, mostly because there can be
cases when you need several requests at the same time. >
Would a case like this be a page having multiple
AjaxSelfUpdatingTimerBehavior
regions ? Our developers are *very* fond of things like this.
I guess so. But as long as you don't update the same area of the page,
this should be ok. Except for the leak. But i _think_ this could be
fixed by requests pooling.
So maybe pooling of XmlHttpRequest(s) could work...
Are you planning on adding this ?
Ari S.
Ari Suutari wrote:
Hi,
There is a browser-side memory leak in wicket ajax stuff when used
with internet explorer. We discovered it when changing our application
from wichet+dojo to wicket+wicket-ajax.
Memory leak occurs only if wicket-ajax is used in IE. With dojo,
there is on leak. Also, in firefox, neither solution leaks.
There is a simple example available at
http://download.syncrontech.com/public/wicketajaxleak.zip
It just displays a number, increments it and displays it again
using ajax.
There is also a memory usage graph which has data from
dojo and wicket-default ajax cases, from that it is easy
to see how differenty these implementations behave.
http://download.syncrontech.com/public/wicketajax.gif
These runs were done agains wicket 1.2-beta3.
This is a rather nasty problem for us, since we have a lot
of pages, which update themselves very frequently based on
data coming from automation systems.
We did some looking around in wicket-ajax.js but didn't
find anything obvious.
Ari S.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
