GWT Server Memory Leak

[Aldo Neto]

Hi,

I'm deploying my app in a local webserver and I'm experiencing a Memory Leak. I analysed the heap with the jmap/Eclipse Memory Analyzer Tool and apparently the objects returned to the client are not being freed. I'm closing all Entity Managers after using them in a search (for instance), but it seems that the objects are still being referenced. Is there any configuration or specific method that I must call in order to get the objects freed?

Thanks,

Aldo

[Thomas Broyer]

GWT-RPC or RequestFactory? Which version of GWT? What are they referenced from?

[Aldo Neto]

Request Factory. GWT 2.3. 

Last question I didn't understand correctly, but after analyzing the heap dump I saw many entities still present in memory. Apparently the entity manager didn't release them completely, although I'm calling em.close() every time.

Tks for you reply.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/oAyEPChLO_gJ.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

[Thomas Broyer]

On Friday, July 27, 2012 4:14:19 AM UTC+2, Aldo wrote:

Request Factory. GWT 2.3.

This is a known issue then, which has been fixed in 2.4: http://code.google.com/p/google-web-toolkit/issues/detail?id=6193

 

Last question I didn't understand correctly, but after analyzing the heap dump I saw many entities still present in memory. Apparently the entity manager didn't release them completely, although I'm calling em.close() every time.

I bet they're referenced from map entries, themselves referenced from the WeakMapping class. This is what I wanted to check with the last question.

[lucyjava]

We have very similar memory leak symptom as described in this post and the bug6193, although we are using GWT 2.6.1, request factory, hibernate, production mode. Please see the screenshot of the heap dump analysis, it is showing the object reference pattern as WeakMapping->ProxyAutoBean->JsonSplittable, is there a fix in the latest GWT code that might address this issue?