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 - > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
