Hello everybody, In my office we are experiencing a very bad problem of memory leak. We are developing an application with GWT based on MVP architecture. Each widget is a MVP and each MVP is based on a own class named DefaultWidgetPresenter. The applicaion has to create periodically new Presenters (subclass of the first) and deletes periodically olders. Anyway application memory grows up. Profiling the application with developer tools provided by Chrome or Safari we registered that Presenter keeps their number increasing slowly and DefaultWidgetPresenter still growing up rapidly, and we don't understand why? We checked if we deleted correctly the presenter and sincerely I can't say "yes" because our probably no deep understanding of GWT technology. This is the application procedure in a nutshell 1) Application create a Presenter dynamically 2) Then it put its displays in a panel 3) Then after a certain time it creates a new Presenter 4) It clears the panel then add the new display. ... and so on
I expected old presenters are garbage collected in some way. In addition I don't understand why we have difference between number of Presenters instances and parents classes instance. I took measurements also from chrome's task manager but I can't understand the relation between profiling and that. In fact when I use profiling the memory grows in a strange way probably because profiling instrument the memory in some way. There is some one that can help us and explain those behaviours? I am wondering also if a key to understand the problem could be understand how GWT implements inheritage and garbage collecting? ? Thank you in advance for any help, this problem is very important. Regards Alberto -- 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.
