I just tried another test. I moved the original RPC call from the onWindowClosed method and put it into the onModuleLoad method and inserted a 3 second delay on the server.
If I refresh the page only after waiting a few seconds, there is no memory leak, but if I refresh the page immediately after it loads, the memory leak returns. It would appear that the leak isn't specific to an RPC call started during the window closing event but rather to the window closing while there is an outstanding RPC request started any time. If that is the case, then we may have a bigger problem because our application uses two second polling for updates and it's probably not unlikely for a user to leave a page while one of those is outstanding. Can we stop the window closing event until the RPC call returns? If we can, I have a feeling we can only abort it and not actually resume the event and either navigate to the other page or close the browser when the call does return. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
