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