IE (especially IE6) has been notorious for leaks...this is neither new, nor specific to GWT. I was working on a "traditional" AJAX application back in 2003 - 2005 (it was a monster!) and we fought memory leaks all the time. One of the big challenges is, as was mentioned, is when you make an RPC call and grab data and "forget about it". You need to be deliberate and exhaustive throwing out data that isn't used and sizing your data fetches to be as small as is reasonable. Another way to investigate is to use Firefox with the Firebug extension. Even though IE is your standard, Firebug let's you dynamically look at the DOM and see what is taking up a lot of space. Another great tool is Fiddler, which will allow you to look at your RPC calls and determine if your application is doing what you think it should be doing. In the past I've seen Fiddler traffic that I thought was only happening once, happen many times and that was causing a lot of size issues.
Then, unfortunately in the end, IE is going to hang onto memory and have problems of it's own and that can't be fixed. And even if you were to move to another browser platform, you're sometimes stuck as the browser is sometimes (emphasis sometimes) not the most efficient way to manage a UI.... Good luck! Later, Shaffer On Mar 13, 6:22 am, Vitali Lovich <[email protected]> wrote: > Just do a lookup through the methods in Document. For instance, iterate > over all children in a depth-first manner to get a feel for the number of > elements over time. Also, if you want, categorize them by something like > tag name. > > It's not the RPC call per se. It would be you making RPC calls, getting > back data, & never freeing references to that data, thereby not allowing the > Javascript garbage collector to free the memory. The reason I asked if you > were making RPC calls is because those tend to generate data and so it's > easy to keep appending/caching data somewhere & forget about it. > > > > On Fri, Mar 13, 2009 at 7:54 AM, <[email protected]> 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 <[email protected]> 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 <[email protected]> > > 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 -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
