With GWT 1.4 + IE, there was a problem with ImageBundles. For each image in the form, IE loaded in memory a copy off the whole ImageBundle. Then, when my app grows, a simple form with a few image-buttons used 200Mb, 300 Mb, 400 Mb... It tought it was a memory leak until we found a great message about that in this group. But this IE problem is better managed by GWT 1.5...
To test it we split a big ImageBundle in two. The memory consumption decrease about a 40%. On Mar 13, 4:20 pm, Jason Essington <jason.essing...@gmail.com> wrote: > If you are using any of the regular GWT methods ... remove() or > clear() or what not, then yes GWT does remove the elements from DOM > and break the circular reference. GWT is very diligent at preventing > memory leaks. That is not always the case if you are using 3rd party > libraries (that may have less diligent quality control procedures), or > trying to do something sneaky with JSNI or DOM methods yourself. > > IE (particularly ie6) is a horrible platform for dynamic web > applications due in part to its incredibly slow javascript engine, and > its penchant for leaking memory like a sieve. > > I tend to not use singletons for UI stuff, so you could try to > instantiate those panels as needed, and simply toss them away when you > are done with them, and see if that doesn't make things any better. > > But again, check what is happening in FF as well and if there is no > leak then you are likely fighting a losing battle against well known > bugs in IE. > > -jason > > On Mar 13, 2009, at 5:54 AM, chauhan.sac...@gmail.com wrote: > > > > > How can we make sure that the GUI objects that we created are actually > > removed from DOM? > > > On Mar 13, 1:58 pm, Vitali Lovich <vlov...@gmail.com> wrote: > >> Make sure that if you remove panels & whatnot from the page, that you > >> actually also remove the DOM element as well as the GUI one. I'm > >> not sure > >> if Google's methods actually do that (if they don't, I think that's > >> a bug). > >> I'll have to look into it though. > > >> On Fri, Mar 13, 2009 at 4:49 AM, LEDUQUE Mickaël > >> <mledu...@gmail.com> wrote: > > >>> We made some tests and found (using very simple application showing > >>> and removing the same UI in a repeated timer) that IE has huge > >>> memory > >>> leaks. > >>> With one add/remove cycle every 2 seconds, we had IE taking 4Gb of > >>> memory in 10 hours. > >>> The others tested browsers (firefox, chrome) didn't have that > >>> problem.- Hide quoted text - > > >> - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
