Dec 11
If you are experiencing OutOfMemory Exceptions while working with Eclipse it could be because your Java VM has run out of PermGenSpace. This occurred with Sun JDK 1.5.0_06 an Eclipse 3.2 using many plugins very often.
To avoid this you may add -XX:MaxPermSize=128m as VM argument when starting Eclipse or add this argument to your eclipse.ini. With never Sun JDKs (>1.5.0_07) it seems that the problem seems to be resolved.
See the bug entry if you are interested.
January 10th, 2007 at 11:10 pm
[...] Until now I thought this happened only in some JDK 5 versions (prior to 1.5.0_08). Adding the MaxPermSize VM argument is needed (see my earlier post). [...]
June 26th, 2007 at 5:34 pm
[...] only in some JDK 5 versions (prior to 1.5.0_08). Adding the MaxPermSize VM argument is needed (see my earlier post). | Save This Post | | Stumble [...]
June 29th, 2007 at 9:44 pm
[...] Before I started Eclipse I looked into the eclipse.ini file and was very happy - the default memory settings for the VM in which Eclipse runs is set to 512 megs and the MaxPermSize setting is there to. In earlier versions you had to add the setting if you are using Sun JDK (see earlier posts). [...]
September 11th, 2007 at 11:48 pm
[...] around. Many of them concerning Eclipse running with Sun JDK 5 and greater - see my posts about JDK 5 and JDK 6. The solution for the problem with Eclipse was to set the amount of memory reserver for [...]