Singleton's are unlikely to cause memory leaks - they will be more responsible for initial startup (although of course it is possible).
One question I would have is whether or not you periodically add data to your application or if you perform queries or RPC calls to some server. That would be a good place to look and see whether or not you are creating objects without clearing. One other request would be to provide the IE version & also test it out on several browsers to narrow it down to a cross-browser issue, or just IE. On Fri, Mar 13, 2009 at 3:37 AM, Sachin <[email protected]> wrote: > > I have a GWT (we are using version 1.5.3) based application having a > large number of forms/screens. It has a single EntryPoint. Application > has become very slow as it takes lot of memory. Now we are running > into memory leak problem, my application sometimes takes huge amount > of memory (more that 200MB) if it is run for a long time in a single > browser. IE is the official browser. > > I have done some investigation and came up with these points: > > 1. Huge Application is using single EntryPoint (only one module). > 2. Application have a large number of Sigleton objects. Even the Main > Panel which is attached to Root Panel is singleton. > > Can someone suggest these Singleton objects cause Memory Leak. Or may > there some other reasons for it. > > Also suggest me what corrective measures I can take to reduce this > problem. > > > Thanks in advance for your help! > > Sachin > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
