If it is an obvious problem in your code, you should be seeing memory leaks in all browsers(which I believe you said you have). If that is the case, you should be able to use the Speed Tracer plugin for chrome. It tells you how many instances of which objects are being created so that you can try and debug where you are holding a reference to the object. Remember, in javascript there is no concept of weak or soft references, so you have to be holding on to an object somewhere in the DOM in order for there to be a memory leak. A memory leak is not something that people here will be able to help you solve directly, we can only give you pointers on ways to narrow down the search. Also, if you are using flash, it is a common source of memory leaks and it would explain the leaks persisting beyond the single page(this could also be explained by a Java applet because only one JVM is used throughout the entire browser).
On Jul 6, 6:15 pm, tarik kandil <tarikkan...@gmail.com> wrote: > First, I would like to mention that I am using GWT2.0. I have a problem in a > data table that I have developed using JQuery, I have many widgets, and I am > using gwittir binding. Besides, I am using bindable collection in my > datatable. After analysing my application, I found that there are some > elements that are not deleted in IE6. Also, the memory keeps incrceasing all > the time. Even if i change to a new page or i refresh the memory keeps > increasing when i filtre or go to another page or I do any action(memory > leak). Can you please tell me how to avoid the increasing of the memory > through the whole application, add methods to delete elements when i go from > page to page, or something like this. Thank you in advance. > > 2010/7/6 Matthias Groß <f0r7y....@googlemail.com> > > > > > Hi, > > > I doubt that you will get any definite answers if you don't provide a > > more thorough analysis of your problem. > > > Generally just try to release all references to heavy-weight objects > > you don't need anymore as soon as possible. This holds true especially > > for global instances, e.g. singletons. > > If that doesn't help consider using weak references (see > >http://java.sun.com/j2se/1.4.2/docs/api/java/lang/ref/WeakReference.html). > > > /Matthias > > > P.S.: > > Also use less exclamation marks please. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google Web Toolkit" group. > > To post to this group, send email to google-web-tool...@googlegroups.com. > > To unsubscribe from this group, send email to > > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-web-toolkit?hl=en. > > -- > Tarik Kandil > Consultant Informatique -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
