We have an app that uses GWT with large HTML content (60-70 K) that produces large memory leaks (2-3 M) in IE 7. It does not exhibit the same behavior in Firefox (memory goes up with multiple document loads, but goes back down after a few seconds of inactivity).
We have looked at the app with the JS memory leak detector which is reporting many memory leaks. This tool reports similar memory leaks for the "kitchen sink" example. Are these "real" or is there something about the GWT code that JS doesn't understand? We know that we are leaking memory that requires browser shutdown to reclaim, but the bulk of the leaks reported by JS seem to be gui components that don't result in significant memory usage. Has anyone else experienced this? How did you solve the problem? Thanks in advance, Chuck --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
