Hi Rob, It is not problem with RPC -calls ,i.e 16k of memory leak is due to gwt-components creation. to avoid this we need to reuse the old references with new state inspite of creating new objects for every RPC call.
Thanks -Kiran.Kuppula On Nov 13, 7:18 pm, Rob <[email protected]> wrote: > I've been trying out one of my existing apps with GWT 2.0 to see what > advantages it has and have noticed a majormemoryleakwhen using RPC > with Internet Explorer 8.0. > > Basically my application reads some values from a database and > displays these in the browser every 1 second. I am seeing amemoryleakof 16k > per second - i.e. every time I make an RPC request the > browser leaks 16k ofmemory. This eventually leads to an out of > virtualmemorysystem error. If I switch back to using GWT 1.7 then > the problem goes away, there are no leaks at all. > > I have managed to reproduce the problem with a very simple RPC example > which I can supply if required. > > Has anyone else noticed anything similar ? > > Cheers > Rob -- 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.
