Hello Dmitry, We are also thinking about splitting application into several. So now we will try this approach starting with creation some "proof of concept" demo application. Thanks a lot for your explanation.
On Jan 16, 12:17 pm, "[email protected]" <[email protected]> wrote: > Hello Alexey, > > Unfortunately this is a typical situation in large GWT application > which uses a lot of custom Widgets and DOM/native code. > > We have found no tooling which would efficiently show us the exact > places of memory leaks and the only approach left is to cut you > application into two halves and see how the memory behaves. > > We have succeeded in reducing the memory leak by carefully analyzing > the code and unlinking custom event listeners and object hierarchies > by overriding onUnload() methods of custom widgets. Splitting your > application into several and providing hard navigation by changing > window.url from time to time, instead of relying on GWT History > mechanism also helps. > > Memory leak situation is a lot better in Firefox and Opera, but Chrome > went further by providing separate memory space for each tab, thus it > guarantees that if you close the tab everything is "garbage > collected", because process is killed. I guess Google took the only > right way to solve the problem :) > > I hope it will help you to deal with your problems. > > Dmitry > > On Jan 14, 4:00 pm, Lex <[email protected]> wrote: > > > > > Hello all. > > > I'd like to ask the question about the approaches normally used to > > manage memory in GWT applications. Till the moment I wrote this post, > > I read most of discussions on the group related to this topik, but > > unfortunately have no answer on my question. > > > What I'm actually looking for: is some guide or list of rules "What is > > necessary to be done in GWT code, to prevent GWT application to > > consume more and more memory". This problem occurs in Internet > > Explorer. > > > Currently we are developing rather big application using GWT. During > > developement process we had noticed that Internet Explorer consumes > > memory more and more and never release it. We had also noticed that > > after we press refresh button in IE, it finally releases most of > > consumed memory (but not all). We try to check out pages with IE leak > > detectors, sIEve, and Microsoft JS Memory Leak Detector. Those tools > > are not detect any memory leaks in our application. > > > After this we create very simple test. We create SimplePanelwidget, > > and put some FlexTable on it. After this we put in this flex table > > different widgets (Buttons, checkboxes, etc.). After we add > > SimplePanel to the rootPanel, and remove it from root panel. Do this > > several times (using timer). After each cycle (add, remove SimplePanel > > from RootPanel) some amount of memory ~200 KB is not released. > > > So my questions are following: > > - Does the situation when IE is not released all memory it consumes > > is know issue or not? > > - Does anybody know what may be done to reduce or remove at all > > memory leaking? > > - Does anybody have URL to some guides of memory management in GWT > > applications? > > > Any help will be highly appreciated- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
