Hi, A couple of good references:
-> http://code.google.com/p/google-web-toolkit/wiki/UnderstandingMemoryLeaks -> http://code.google.com/p/google-web-toolkit/wiki/DomEventsAndMemoryLeaks Cheers Rob http://code.google.com/p/gwt-cx/ On Nov 9, 5:49 am, Mark Allerton <mark.aller...@gmail.com> wrote: > Hi, > > I'm sure I'm not the only person who has ever thought that it might be > possible to use Java-based heap profiling tools to look for memory > leaks in GWT-based applications, but in practice this has turned out > to be a little frustrating because at least based on my naive > interpretation, Hosted Mode leaks pretty much every object that needs > to be invoked from the native side, apparently by design. > > So my question is, am I missing something? > > To be more specific about what I am seeing, I see many many objects > referenced only via the ThreadLocal "dispatchObjectCache" in > JsValueOOPHM. As far as I can tell based on searching the source code, > objects are only ever put into this cache and none are ever removed. > > I have had some (apparent) success with the Eclipse Memory Analyzer, > which allows me to exclude refs via Thread.threadLocals when tracing > from GC roots, but I want to be sure that the references I am > excluding can in fact be ignored (i.e there is not some way that > objects are removed from dispatchObjectCache that has escaped my > attention.) > > Thanks in advance > > ..Mark.. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
