- This topic has 6 replies, 5 voices, and was last updated 15 years, 4 months ago by
.
-
Posts
-
Hi guys,
I’ve just upgraded to MyEclipse 8.0 (clean install) and am having difficulty increasing available memory. First I tried editing myeclipse.ini, but after any change there (eg. I tried Xmx1024m, also -XX:MaxPermSize=512m, also -XX:ReservedCodeCacheSize=128m) MyEclipse simply fails to start, reporting (in an alert box):
JVM terminated. Exit code=-1 -Xmx1024m -XX:MaxPermSize=256m -XX:ReservedCodeCacheSize=64mI get the same thing if I try to edit the shortcut:
"N:\Program Files\Eclipse\MyEclipse.0\myeclipse.exe" eclipse.exe -vmargs -Xmx1024mIs this expected? What is the ‘correct’ way to increase available memory?
Regards,
Richard.
Richard,
Sorry to hear you are running into this issue. Can you answer few queries for me to get to the root cause?
1. Can you copy and paste your installation details? Open MyEclipse IDE, from menu options click on MyEclipse > Installation Summary > Installation Details.
2. Can you copy and paste the contents of your myeclipse.ini file?
3. Why do you want to increase memory?As requested, installation details:
*** Date: Monday, 30 November 2009 9:20:13 PM EST ** System properties: OS=WindowsXP OS version=5.1.0 Java version=1.6.0_13 *** MyEclipse details: MyEclipse Enterprise Workbench Version: 8.0 Build id: 8.0-20091120 *** Eclipse details: MyEclipse Enterprise Workbench Version: 8.0 Build id: 8.0-20091120myeclipse.ini
-startup ../Common/plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar --launcher.library ../Common/plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519 -install N:/Program Files/Eclipse/MyEclipse/8.0 -vm N:\Program Files\Java\jdk1.6.0_13\jre\bin\client\jvm.dll -configuration configuration -vmargs -Xmx512m -XX:MaxPermSize=256m -XX:ReservedCodeCacheSize=64mI want to increase the memory because it is my understanding the Ant builds run within the same VM as Eclipse, and my Ant builds are running out of memory.
Regards,
Richard
Richard,
When VM startup immediately fails it’s usually due to the memory args being *too* big, the VM is unable to grow to that size typically and blows up.
Also from the ‘External Tools’ menu is where you can edit the launch configurations for your Ant scripts, you will want to set the additional memory for them in there, for the VM args directly, it launches in an external process.
