Hi Maddy, Have you made sure that your issue is the same as the one Gordon experienced? It is possible that outstanding RPC calls that didn't return are causing memory leaks, which in turn are causing your application to freeze (see Issue #1304 below), but the fact that the issue you described where the user closes the child browser window and re-opens it, and then re-opens it might suggest that there's something else going on.
Issue #1304: http://code.google.com/p/google-web-toolkit/issues/detail?id=1304 If you could isolate the cause of the freeze in your application to a smaller code snippet, that should help reproduce the problem on our end to see what's going on. If you are experiencing the same issue Gordon described, then you can cancel the requests by maintaining a list of Request objects returned by the RequestBuilder.sendRequest() call, and invoking cancel() on these when the window close event happens through a CloseHandler. However, canceling the request means just that, so the server may not receive the call at all. Issue #1304 aims to fix the memory leak problem, so you shouldn't have to resort to this workaround for too long. Hope that helps, -Sumit Chandel On Wed, Jun 10, 2009 at 7:52 AM, Maddy <[email protected]> wrote: > > Any thoughts on this? Please help me. It is very urgent. > > On Jun 5, 5:58 pm, Maddy <[email protected]> wrote: > > Hi gpike, > > > > Thank you very much for the information.Can you little bit explain > > more how to handle the outstanding rpc requests? > > > > Maddy > > > > On Jun 5, 4:02 pm, gpike <[email protected]> wrote: > > > > > Hi Maddy, > > > > > We had the same issue. What we found was if the window was closed > > > while an rpc request was outstanding a port was blocked so subsequent > > > calls would fail. To fix it we had to track and abort any rpc requests > > > in a IWindowCloseListener. > > > > > Gordonhttp://devbright.com > > > > > On Jun 5, 12:52 pm, Maddy <[email protected]> wrote: > > > > > > Hi, > > > > > > My GWT application gets launched in a child browser from another > > > > parent brwoser. When the user closes the browser, while the GWT > > > > application is running and when he launches back the application > > > > again, IE hangs and it is just a blank screen.. > > > > > > This is not happening all the time and it happens occasionally. > > > > Application works fine in Firefox. > > > > > > Could anybody help me with this, as this is becoming a serious issue. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
