If you ever need to increase Eclipse 3.1's startup min max memory settings consider modifying the vm settings in the file eclipse.ini to increase your memory heap.
While Eclipse 3.1's default memory size has been increased to 40M minimum heap and 256M 512M maximum heap, it may not be sufficient . In my case, my earlier versions of Eclipse (pre 3.1) my JVM continually crashed when loading up Sakai projects--the result perhaps of extending the Eclipse IDE to use MyEclipse 4. 0 M2 (although my JVM continued to implode even after deactivating a gaggle of MyEclipse Genuitec plugins normally activated on startup). Changing my startup min max memory settings appears to have righted the good ship Eclipse so I thought I would share my experience.
...
My changes (for the moment):
No Format |
---|
-vmargs -Xdock:icon=showsplash org.eclipse.platform -startup ../../../Resources/Eclipse.icns -XstartOnFirstThread -Xbootclasspath/p:plugins/org.eclipse.equinox.launcher_1.0.101.R34x_v20081125.jar --launcher.library ../../../plugins/org.eclipse.equinox.launcher.jdtcarbon.debugmacosx_3.1.0/jdi.jar -Xms256m -Xmx512m -Dorg.eclipse.swt.internal.carbon.smallFonts.101.R34x_v20080731 -vmargs -Xdock:icon=../Resources/Eclipse.icns -XstartOnFirstThread *-Xms128m* *-Xmx1024m* *-XX:+UseParallelGC* -XX:MaxPermSize=256m -Dosgi.requiredJavaVersion=1.5 -Dorg.eclipse.swt.internal.carbon.noFocusRingsmallFonts |
Default settings
No Format |
---|
-vmargs -Xdock:icon=showsplash org.eclipse.platform -startup ../../../Resources/Eclipse.icns -XstartOnFirstThread -Xbootclasspath/p:plugins/org.eclipse.equinox.launcher_1.0.101.R34x_v20081125.jar --launcher.library ../../../plugins/org.eclipse.jdt.debug_3.equinox.launcher.carbon.macosx_1.0/jdi.jar.101.R34x_v20080731 -vmargs -Xdock:icon=../Resources/Eclipse.icns -XstartOnFirstThread -Xms40m -Xmx256mXmx512m -XX:MaxPermSize=256m -DorgDosgi.eclipse.swt.internal.carbon.smallFontsrequiredJavaVersion=1.5 -Dorg.eclipse.swt.internal.carbon.noFocusRingsmallFonts |