I'd suggest running Microsoft's memory leak tool and working out which elements, exactly, are leaking in your app and why.
Once you know that you can purge them by hand -- this is how I started. I only went into this Widget hack because the list of items I needed to deal with was... really long. :) That said - QA has a different use-case that still leaks in our app as well, so... the story is evolving. I'll update the thread if we find out more in case it's helpful for others. Best of luck! Regards, Paul On Nov 8, 4:31 pm, chrisr <[email protected]> wrote: > Thanks jay, got that sorted out. I can confirm via breakpoints that > in hosted mode (we're on GWT 1.5) the NoMemLeaks implementation is > getting used, but unfortunately it doesn't fix our memory leak in IE. > > Is there a simple way to verify that its actually getting used by IE? -- 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.
