emh....if i do a F5 (aka refresh) it doesn't free memory at all!! Only increases memory occupation with new elements.... :( strange isn't it?
2009/7/20 Adam Fredericks <[email protected]> > I have just come to accept these memory leaks, and in so doing I just > ensure that every design I do using GWT-Ext reuses as many elements as > possible or is split between multiple pages so that the browser refreshes, > which is the only real way to retrieve memory in IE6+. You’ll spend the same > amount of time trying to plug leaks as you would approaching any design from > that perspective – in my opinion. And if you’re clever with the design, the > end result ends up providing a much better user experience. > > > > Adam > > > ------------------------------ > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *Patrizio De Michele > *Sent:* Monday, July 20, 2009 7:09 AM > *To:* [email protected] > *Subject:* Re: GWT EXT Memory Leakage > > > > looking at sources you(we) don't need to deAttach listeners is done > automatically... > but just to be sure i'm overriding onDestroy method and clearing as much as > i can. > for example i have a window that isn't destroyed automatically... > bye Pat > > 2009/7/20 Patrizio De Michele <[email protected]> > > ok we got the same problem.....NOTHING is released :( > memory is always growing.....:( > it's a very huge problem for me.... > i'll start with removing listeners... > > 2009/7/20 Patrizio De Michele <[email protected]> > > > > try to remove all listeners....and also to check if it is called > the onDestroy event if it is called it should be enough to grant > that garbage will be called. > I believe that simply settings null isn't enough maybe a direct > call to destroy method is better, probably will release a lot of > resources....if not all.... > make me know i'm also interested on this problem and i believe > that sooner or later i'll meet memory leakage problem on my app... > at the moment isn't so heavy.... > bye Patrizio > > 2009/7/20 SunilBansal <[email protected]> > > > > > HI All, > > > I am facing memory leakage problem in my application. I searched on > Google but i found that memory leakage may be because of EXT JS > because of some cyclic references in between JSNI and DOM objects and > browser is not able to handle these DOM objects for garbage > collection. > > I am using following technologies in my application : - > > GWT 1.6.4 > GWT EXT > Gilead > > > When i explorer my code then i found some reason that may be cause of > Memory Leakage as :- > > 1.) While i am clearing the widget or setting it's reference to null > then i am not removing the listeners explicitly. > > > But i am feeling, this memory leakage is not only because of this not > removing listener explicitly and now i am not able to understand how > can i remove this problem. > > So, please tell me if anybody have an idea? > > > Thanks and regards, > > Sanj > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GWT-Ext Developer Forum" 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/gwt-ext?hl=en -~----------~----~----~----~------~----~------~--~---
