Community
Participate
Working Groups
I've been using Eclipse for a long time, and it's worked fine, but suddenly the workbench won't open anymore. When I run eclipse.exe, the splash screen shows up, then I get a "VM terminated with exit code 13" message and eclipse never starts (incidentally, in this case the splash screen won't go away unless I use the task manager). I get a new, very short log file every time I try: !SESSION 2005-02-27 13:21:03.848 ----------------------------------------------- eclipse.buildId=I20041216-2000 java.version=1.5.0-beta java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86 !ENTRY org.eclipse.osgi 2005-02-27 13:21:03.848 !MESSAGE An unexpected runtime error has occurred. The application will terminate. !STACK 0 java.lang.OutOfMemoryError: Java heap space Since I'm fairly sure this is of no help to you, I'm including the 25KB .log file that seems to have caused this. I regret that I can't tell you what I did differently that made eclipse stop working (maybe I closed it while there was a running Java program?), but I certainly didn't change any config settings. Also, I don't need to maintain my workbench settings - if there's some magic quick-fix, like deleting a config file so it uses the defaults, I'd be fine with that.
Can you make a try with Sun 1.4.2 VM which is the recommanded version for Eclipse. Can you also add vm argument -Xmx256M and let us if it fixes your issue. If this fixes your problem then close. Reopen otherwise, thx
1) Sorry my big .log file isn't included. I can't seem to get Bugzilla to remember me as logged in, even though Firefox has cookies enabled, and it forgets who I am between entering the file to attach and submitting it. 2) So I should just add "-Xmx256M" to the list of arguments for my eclipse.exe shortcut, or do I have to prefix something to flag that as a VM argument? 3) How do I specify what VM to use for eclipse? (Sorry I'm reopening this without having tried your suggestions yet, but I don't know how to try them, and I'm not actually sure my comment will get to you on a closed bug)
You can specify VM in eclipse.exe line argument using -vm parameter. If you do not, then you'll use one specified in you path... To specify argument to vm, then use -vmargs parameter. So, yo increas VM heap size, add -vmargs Xmx256M at then end of your command line. See <install_dir>\eclipse\readme\readme_eclipse.html file...
With JDK 1.4.2 and the following commandline: eclipse -vm C:\j2sdk1.4.2_07\jre\bin\javaw -vmargs Xmx256m I get a different error message: a window pops up telling me it could not find the main class - it looks the same as when you run a jar file with no manifest using java -jar. If I change it to eclipse -vm C:\j2sdk1.4.2_07\jre\bin\javaw -vmargs -Xmx256m (Note the - in last argument), I get the same error message I've been getting previously. The .log file also appears similar, but with a different setting for java.version: !SESSION 2005-02-27 17:29:28.691 ----------------------------------------------- eclipse.buildId=I20041216-2000 java.version=1.4.2_07 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86 !ENTRY org.eclipse.osgi 2005-02-27 17:29:28.701 !MESSAGE An unexpected runtime error has occurred. The application will terminate. !STACK 0 java.lang.OutOfMemoryError
Of course -vm -Xmx256M was the right way to set VM heap size... Perhaps, if your box as enough memory you can try to increase it to 512 or 1024? Can you also try with last milestone 3.1 M5a as it seems you still have M4 installed.
Okay. Getting M5a worked. I suspect just reinstalling M4 would have worked too, but I'm not complaining.
Reopen to change bug resolution...
Close as INVALID (ie. it seems not to be a JDT/Core bug and nothing has been changed in code)
