gwt /
gwt /
a615718a29a75d32737821b93344195d59acf85e Attempts to do the following:
1) Cleanup all outstanding non-primitive properties from $wnd
2) Remove all registered event listeners
3) detach all widgets from rootpanel
4) Cancel any continuously running timers, I/Os in progress, etc
5) Delete all code from the iframe scope (window != $wnd)
6) erase registration from __gwt_activeModules and null out nocache.js module function
7) Remove iframe hosting the module (if present)
Even with all of this cleanup, Chrome's heap profiler still shows leaks on the simplest modules. This is a work in progress to support portal-like services that want to load/unload many GWT modules within a long running page.
Currently, IE paths which use attachEvent() have not been patched.
By default, support is disabled and there should only be a negligible impact on codesize.
Review at http://gwt-code-reviews.appspot.com/1827804
Review by: skybrian@google.com
git-svn-id: https://google-web-toolkit.googlecode.com/svn/trunk@11539 8db76d5a-ed1c-0410-87a9-c151d255dfc7
24 files changed
