Comment by atul.dambalkar:
We also have quite a big GWT based application. In our application, we have
also seen similar memory issues showing up in FireFox3.6, IE and Chrome4.1
as well. Browsers eventually stopped responding (with CPU more than 70%)
after memory reaching up to 1GB (happened with Firefox 3.6, this happened
under a load test scenario though).
I tried with the above sample code. (Thanks for the code BTW, it's very
useful to re-produce the problem quickly) And observed similar memory issue
on all the browsers. What I have observed is, on Firefox 3.6 (Windows XP)
memory does keep going up all the time but not every time it gets
reclaimed/goes down. It goes down very intermittently. I guess that fact
might very well be attributed to the way JavaScript engine's garbage
collection works or gets kicked-in.
I debugged the above code with certain modifications and did see that once
cleared from the panel, the new elements do get unattached/removed from
browser's DOM(so there may not be memory leaks), but that doesn't really
make browser's memory to go down immediately. I am not entirely sure, but
if it is due to the fact that perhaps the JavaScript engine's GC is not
getting kicked in frequently, is there any way we can hint/force Firefox to
run the GC? Or is there any way GWT can provide so that we can force
browser to run JavaScript GC.
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.
