OOPHM memory leak?

[Dominik Steiner]

Hi there,

I'm using eclipse 3.5 on Mac OSX with the google eclipse plugin and
GWT 2.0.

What I see is that every time I reload my gwt app that I'm debugging
using the Web Application launch configuration from the plugin and
OOPHM in Firefox 3.5, the memory usage of the java process that is
being started when i start the Web Application via OOPHM is constantly
rising until reaching 400 MB where i get an OutOfMemory exception.
Basically I can thus only 4 or 5 times reload the web page until
having to close the Web Application from within eclipse and start a
new one. Besides that I'm seeing that everytime I launch a new Web
Application (having terminated the prior one) the threads in my
eclipse process is steadily rising too, so that after a while i get
like > 150 threads which is bring down my eclipse performance.

I really like the way OOPHM works, but did someone else experiment the
same performance/memory problems while using it?

Thanks for any hints you can give me

Dominik

[kozura]

Same setup, I do see a slow increase of about 10-20MB per page upload
in the Developer application. Eventually this might lead to out of
memory exception; you could always increase the heap size for now to
avoid that for awhile longer, -Xmx512 or whatever. I see nothing
maintained in the app that should be causing extra memory to be take
for each reload, so seems there may be a legitimate memory leak here.

I don't see the consistent thread increase, although it does seem to
go up by one occasionally on restart.

[Dominik Steiner]

Thanks kozura for your reply,

here with me I see an increase of around 40 MB on each reload, and my
app already starts with java allocating 200 MB on the first load.

Not sure if the project size correlates with the amount of memory that
leaks, here with me I have around 700 classes on my project?

Also not sure what eclipse is doing in the background and perhaps is
holding the threads until garbage collecting them, but I see 3 new
threads added each time when i relaunch the application.

Thanks again for your information

Dominik

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

[kozura]

I'm sure the project size probably does affect the amount, these are
fairly significant chunks of memory to be adding for every reload.
I've not done java leak debugging with its gc, and am not familiar
with OOPHM details enough to know what to look for, so might be a good
idea to post an issue on the memory leak. At least bumping heap size
to 1G or somesuch should reduce the frequency you have to restart.

[Sky]

This is an old thread, but I'm experiencing a similar out of memory error using the GWT 2.1 and AppEngine 1.40. This happens when the javaw.exe exceeds 512mb.

I have -Xmx512m set. I must have set that a long time ago because I don't remember doing that.

But if I reload my app around 15 times I run out of memory. Not the end of the world, but I'd like to know if I'm doing something wrong in my web app. I don't want the browser tab to be using up tons of memory if I'm doing something wrong. I suspect that this issue doesn't affect the browser, but I want to be sure.

[Jim Douglas]

http://code.google.com/p/google-web-toolkit/issues/detail?id=4923

[Thomas Broyer]

See also http://code.google.com/p/google-web-toolkit/issues/detail?id=5486 (fixed in 2.1.1)

[Fille]

I have had this problem for a while now. After i have refreshed the browser/server a couple of times the process javaw.exe is about 2GB, and it is so slow.

How could this be fixed?

Using latest GWT eclipse plugin, java6, gwt 2.5. I have tried different perm-gen/heap sizes, that just fix the OutOfMemoryException.