My mistake, this actually only "fixed" the memory leak because it was throwing a js error that prevented the code from continuing on to leak memory.
On Oct 11, 11:32 am, chrisr <[email protected]> wrote: > Got pulled off to work on other issues, finally coming back to this > again. > > I managed to find a way to fix one of the memory "leaks" in the > application. I was under the impression that you didn't have to > explicitly remove things from the DOM in this way, so I'm curious why > it seems to solve my problem. > > Basically I changed this: > > public void doSomething(){ > panel = null; > > } > > to > > public void doSomething(){ > if ( panel != null ) { > DOM.removeChild(RootPanel.getBodyElement(), > panel.getElement() ); > panel = null; > } > > > > } -- 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.
