Comment by [email protected]:
I'm not aware of any way on most browsers to force a GC. On IE, there's the
global CollectGarbage() function, but IE already runs GC too frequently
most of the time anyway, so it's not much help. I'm less familiar with
Firefox and Safari, but Chrome's GC is generational, so there are several
different kinds of collection and compaction, but again I don't believe
there's any way to force it.
As I noted above, I didn't see the example posted by GlacieredPyro leaking
in any obvious way. If you can post a (preferably small) example that
causes the browser to run slowly and/or consume an enormous amount of
memory, but that doesn't just have an enormous number of objects pinned
(i.e., referenced globally or indirectly), I can forward it to the Chrome
team so they can have a look.
For more information:
http://code.google.com/p/google-web-toolkit/wiki/DomEventsAndMemoryLeaks
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
To unsubscribe, reply using "remove me" as the subject.
