Comment by j...@google.com:
I've run through this with IE7, IE8, Microsoft's IE JS Leak Detector, and
Chrome, and I'm not seeing any evidence of it leaking, on IE at least. On
my Vista box, memory grows steadily as I add more items, then mostly
recovers as I clear or reset. There is a gentle upward trend in total usage
as I do this, but it appears to peak out at around 30MB and no longer grows
after that.
I'm seeing Chrome's "private memory" grow without obviously slowing down,
but I have to admit to not being too clear on the details of what to expect
from its generational GC. I can ping some people on the Chrome team about
that, but my guess is that it's going to end up being that it never ran low
enough on memory to be worth running a major GC cycle.
For more information:
http://code.google.com/p/google-web-toolkit/wiki/DomEventsAndMemoryLeaks
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
