Large memory leak in IE8 when GWT runs on a new Window

[Reuben S]

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

[stuckagain]

Hey,

 

I seem to be seing similar issues when putting a GWT application in an IFrame and then removing the IFrame. It looks like the entire GWT application leaks.

 

I saw your bug report in the bug tracker of GWT. I added my comment there with a suggestion on how they could maybe fix this issue without impacting the few that would want to install a onwindowclosing handler that calls setMessage. This will ofcourse need a fix in GWT (the sooner the better since we are leaking about 40MB everytime we close the IFrame, and unfortunately we need to do this often in one browser session).

 

David