We have a number of fairly large GWT/GXT screens in our application, most of them run 'embedded' in our application main window, which includes a mix of 'legacy' client code and areas of GXT code. Navigating to and away from pages containing GWT code does not show any significant memory leaks in IE8.
Now some of our screens pop up a new Window running complex GXT code. In those applications the top GWT-generated code attaches to the RootPanel. Closing the window associated with such an application leaks typically 80 MB (!!!) in IE8. We found a workaround by having IE run the new Window in a new process, in which case the huge leak still exists, but IE eventually kills the new process within 60 seconds of closing the Window. Now we have scenarios in which we need to run the pop-up window in- process. I wonder if someone can think of a reason for the large leak in this scenario. We are using GWT 2.0 with GXT 2.2. This issue reproduces (at least) on Windows 7/64 bit (with IE in both 32 and 64 bit mode) and on Windows XP (we don't test Vista). No leaks are observed on Firefox, even though FF runs new windows in the same process. Any help will be greatly appreciated. Thanks, Reuben -- 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.
