[news.eclipse.newcomer] Re: Eclipse hates me! Help requested please:

[Kevin Crocker <kevin@xxxxxxx>]

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.


> I've never seen such tool.
> I can assure you that if Eclipse is indeed running in a Sun JVM it will 
> set the Perm Gen size with that option. Can you confirm the JVM that 
> Eclipse is running in (Help > About Eclipse > Configuration Details)

I can assure you that I am running SUN's JVM because that's all that's
installed on this machine. 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.

> 
> 
>> I'm still getting OOME (Out of Memory Errors) that point to PermGen
>> (MyEclipse pop up). I went through and read the complete Bug report on
>> this and while it was tremendous, it appears that this problem resides
>> in the SUN JVM and there doesn't seem to be much movement on fixing it.
> 
> Sounds like MyEclipse should be told about your troubles, too. It is
> their tool that is telling you there is a Perm Gen problem, and likely
> their plugins that are causing it to go over the default 64M limit.

No, you misunderstand. It is not their tool that is causing the problem,
they are simply creating a popup window when the JVM issues a OOME with
the message pointer saying it's PermGen that caused the OOME.

I suggest you read the above bug discussion. I found it shortly after I
had posted this thread.

>
> Hope this helps,
> 	Eric


Yes, thanks. Every little bit helps.

Kevin