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 -~----------~----~----~----~------~----~------~--~---
