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
