On Tue, 31 Jul 2007 12:10:11 -0400, Eric Rizzo wrote:
Kevin Crocker wrote:
Thanks for the explanation. It helps a lot - unfortunately, the --launcher...
one doesn't actually set the MaxPermGen higher than 64M - I tried this
and set it t0 128M and the Memory Monitor still says that PermGen is set
to 64M
What "Memory Monitor" are you talking about that shows Perm Gen size?
The memory monitor that is listed as an attachment in the eclipse Bug
for PermGen, I think I still have it as a gz file and could send it to you
or post it somewhere --- or I could go and find the bug at eclipse again
https://bugs.eclipse.org/bugs/show_bug.cgi?id=92250
It's listed as a tweaked version of Memory Monitor and it shows a bunch
of nice bars - but if you hold your mouse over each bar it tells you
what the bar means and it's size -- try it out
now, of course, I could be getting led down a garden path, but I doubt it
as this bug discussion is mostly by serious eclipse coder types.
And I can also assure you that despite
setting the MaxPermGen with the --launch (which by the way was already
set - the eclipse people did that automagically upon detecting SUN JVM)
or by setting it manually and experimenting with different values,
it does not change the PermGen size. I've read through all of SUN's
documents on this too, and even SUN says that the -X and -XX parameters
are not guaranteed to work. This one doesn't on my machine.
You can always try forcing the max perm gen setting to your JVM by
adding "-XX:MaxPermSize=128m" (line by itself, without quotes) after the
-vmargs line.
I did that too - I changed this 12 times to different numbers, and every
single time, the Memory Monitor showed that I always had 64M --- but more
importantly, Eclipse 3.3 kept dying after a very short time - sometimes
as little as one or two clicks.