Thanks jay, got that sorted out.  I can confirm via breakpoints that
in hosted mode (we're on GWT 1.5) the NoMemLeaks implementation is
getting used, but unfortunately it doesn't fix our memory leak in IE.

Is there a simple way to verify that its actually getting used by IE?

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Reply via email to