Hi Damon, Thanks for tracking this down. You're absolutely right, this is something that GWT should be able to handle for you. I've updated Issue #1304 to re-ping Joel on it. He should get back to use on the issue report.
Cheers, -Sumit Chandel On Thu, Jun 18, 2009 at 2:54 PM, Damon Lundin <[email protected]>wrote: > > I've tried adding the HTTPRequestImplCleaner.java class to my project > that attached to that issue but none of the methods on it seem to be > getting called. I did verify that's it's getting instantiated but I > suspect that this is based off of old code and no longer works against > the current http request implementation (we're using GWT 1.6 now). > > However, taking a hint here, I have tried something that does appear > to give us a workaround. If I have my RPC method return the Request > and then immediately call cancel on the request, the request is still > sent to the server, but the memory leak disappears. We should be able > to do that for our oustanding poll requests as well - keep track of > them and cancel them in onWindowClosed. > > This definitely seems like something that GWT could handle for us and > auto-cancel requests when then window is closed. Perhaps that's what > the patch in the 1304 issue was meant to do. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
