it may just be the way the error shows (and not how it is written in the eclipse.ini file), but there is text in eclipse.ini (specifying the jvm) that says the following:
- the -vm option and its value (the path) must be on separate lines.
- the value must be the full absolute path to the java executable, not just to the java home directory.
- the -vm option must occur before the -vmargs option, since everything after -vmargs is passed directly to the jvm
well, it better not be eclipse 3.1.x and java 7. i resolved this combination by upgrading to eclipse 3.8.x.
i had the same issue on ubuntu, and solved it by unpack all *.pack files in jdk directory. for example: cd /usr/java/jdk1.7.0_03/jre/lib sudo ../bin/unpack200 rt.pack rt.jar
use the configuration below;
i fixed it reinstalling the jdk. in my case it was necessary to do:
sudo apt-get purge openjdk*
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java7-installer
in my case java path was not set in env variables. started to work after correct path was set in env path.
type javac in command prompt and make sure java path is correct.
i did couple of things inorder to get rid of this annoying error as modifying .ini never worked for me.
- installed latest jdk
- delete old eclipse ide folder completely.
- this time i unziped to different location
double click "eclipse.exe" works now like charm use default workspace to load your old projects.
am suspecting it to be jdk's java vm issue more than eclipse.
i used the new eclipse installer. i didn't like the installation path and i changed it manually. after that, i got the exit code=13 message too.
there is a new property in the
eclipse.ini file named
-install. i just had to modify it with the new location, and that solved this issue.
in the new installer i selected
d:/eclipse, but the ide was installed at
d:/eclipse/eclipse. so, i moved the folder manually. the next time i tried to open eclipse i got the exit error. thus, i had to modify
eclipse.ini and set the current location:
before going to the solution, let us know why it is showing that error. if you know the problem behind this issue we can easily fix that error.
reason 1: the most common reason behind this problem is, we are trying to install different bit version-that is, 64 bit or 32 bit version of the software. it maybe either eclipse or java.
solution: check which version of operating system you are running.make sure you downloaded the same version of eclipse as well as same version of java software.
reason 2: configuration mistake in eclipse.ini file
solution: add this line "-vm then path of your java sdk" at the end of eclipse.ini file. for example: -vm c:\program files\java\jdk1.7.0_71\bin\javaw.exe
reason 3: special characters ( #, !, @) in eclipse installation directory.
solution: make sure you don’t have any special characters.
reason 4: you have added java path two times in path system variable and both the path are different.
solution: remove one incorrect/different java path from path system variable.
reason 5: you maybe using latest version of eclipse, but you might be using wrong version or unsupported version of java virtual machine (jvm).
solution: to check which version of java you are using open command prompt by pressing win+r key and type cmd and press enter. now in that console type java -version command to know java version. now research whether eclipse support that version or not. or you can open “readme” folder in eclipse folder and open readme_eclipse.html to see which version it supports.
for ones with eclipse neon
i wanted to run eclipse neon and had jre 1.8 but jdk 1.7 it returned error=13 then i installed java jdk 1.8 and everything worked like a charm
i had this issue also. i had an old jdk1.8.0_05. i installed the newest jdk1.8.0_111 and everything works great now. just be sure to update your environment variable.
i am on windows 7 64 bit. using eclipse neon 1a.
hope that helps someone.
i face same issue with sts 3.8.4, so i tried different settings but not luck, i reinstall jdk again n tried but same problem. finally i downloaded sts 3.8.2 n it runs with out any issue. using windows 8, 64 bit os. thanks
this can happen when the path environment variable is point to a wrong java instalation.
1 ) open the springtoolsuite4.ini file.
2 ) search for the "openfile" text in the springtoolsuite4.ini file.
3 ) provide the javaw.exe file location in springtoolsuite4.ini
4 ) note : provide the new line between -vm and your javaw.exe file location path as shown below.
i tried many way and placed -vm argument at suggested place. but it would not work. finally i got solution. -vm args should be place eclipse.ini file before execution of any plugin or jar. i tried with latest eclipse [photon ] in ubuntu 18.04 it is perfectly working for me.
in my case i install java 64 bit and used 64 bit eclipse and the error is gone. you can make combination like this
- 64 bit java - 64 bit system - 64 bit eclipse
- 32 bit java - 32 bit system - 32 bit eclipse
- 32 bit java - 64 bit system - 32 bit eclipse
in all these cases we'll never see this error.
this error occurred to me on ubuntu, having installed 32bit and 64bit java. use
sudo update-alternatives --config java
to set the right version to use as default.
just uninstalled jre-32 bit version and it worked fine for me.
i was using eclipse juno and i didn't remember if it was 32 or 64 bits. i installed java 32 bits and that's why it failed. i then installed java 64 bits and eclipse juno is working again.
i also removed any java or jre reference in my environment variables (path).
in my opinion the most answers here regarding different architectures of eclipse and java are simply wrong and this can be easily checked using e.g. process monitor under windows. the
-vm option is there to run a specific version of java and the point of it is, that the configured process is started and runs all the java code on its own, that's why you configure up to
java.exe. in that case you don't need to have the same architecture for eclipse and java, but can happily mix both 32 bit and 64 bit. you only can't mix both, if you don't use
-vm, but let eclipse load java natively into its own process using jvm.dll and such. that latter behavior is eclipse's default, but not the case anymore if you properly configure
if you don't believe me, do some tests on your own using different architectures of eclipse and java and do configure
-vm or not properly. in the end, that's exactly what the questioner described in his comment to the accepted answer:
he is telling that a 64 bit jdk is working now, but in his screenshot one can see that his eclipse is 32 bit, because the path for
launcher.library is 32 bit.
and now for the reason i came here: ony of my customers had some problems loading one of our eclipse/osgi based applications as well and java exited with exit code 13. in the end it showed that the problem was not about
-vm or the architectures of java and
eclipse.exe, but instead he was simply missing
config.ini and i guess
eclipse.exe wasn't aware what to load or such. after we recognized that and put a
config.iniback in place, the app loaded fine with using
-vm and a 64 bit jre7 in combination with a 32 bit
i had the same issue with eclipse in my both machine. i had jre 32 bit installed. so i removed 32 bit and installed 64 bit instead and it worked perfectly.
simply install 64 bit version of java from http://java.com/en/download/manual.jsp
and uninstall older version if prompted by the 64 bit installer
go to the folder where you saved eclipse. look in the configuration folder at the startup log. it will give you a much better diagnostic than "exit code 13".
after java update, eclipse will not start because default jdk location has changed. adding the following lines to eclipse.ini file solved my problem immediately:
c:\program files (x86)\java\jdk1.7.0_75\bin\javaw.exe
i added these lines just before vmargs. it looks like as the following :
c:\program files (x86)\java\jdk1.7.0_75\bin\javaw.exe
for more information on eclipse.ini, visit this the site http://wiki.eclipse.org/eclipse.ini#-vm_value:_windows_example
in my case, i use 32 bit eclipse and java. if you installed both 32 bit and 64 bit versions of java, be careful to choose the right version. for 64 bit versions, refer to the javaw.exe file under the directory
whenever you see this error, go to configuration directory and check for a log file generated just now. it should have proper exception stacktrace. mine was a case where i got an updated 32-bit jre (or jvm) installed which was the default java that got added to the path. and my eclipse installation was 64-bit which meant it needed a 64-bit vm to run its native swt libraries. so i simply uninstalled the 32-bit jvm and replaced it with a 64-bit jvm.
i wonder if they will improve this reporting mechanism, instead of silently generating a log file in some directory.
i just had the same issue, and spend about an hour trying to solve the problem. in the end it was a '#' character in the path.
so i renamed "c:\# ide\eclipse 3.7\" to "c:\+ ide\eclipse 3.7\" and that solved the problem.
recently i faced same issue.my version of eclipse didnt support java version 8.
i had accidently installed jre 8 on my machine which automatically updated my path variable by appending "c:\programdata\oracle\java\javapath" in the beginging which led eclipse to pick up this version(and ignore the manually added 1.6 version which came later in order)and crash with exit code 13.
i just removed this string from the path so which led system to pick up my older version and eclipse started just fine.
make sure the eclipse and the java that you are using are both either 32-bit or 64-bit.
you cannot run 64-bit eclipse with 32-bit jre.
64-bit server vm
the 32 bit version jre will not have 64-bit in it.
the error means it's the wrong jvm version for that version of eclipse. the link has more details:
i just hit this too. turns out that at least for me, this was due to trying to use a win64 version of the jre with a win32 eclipse. i seems that win32 eclipse requires a win32 java (what is called -586 in the list of java installers from oracle/sun).
the reason i was using both is that i was trying to pinpoint a bug that only manifested itself in 64-bit eclipse, so i needed a 32-bit to compare to.
once i installed both the "x64" (win64) and "i586" (win32) versions of the jre on my machine, things work fine and no error 13. you can apparently have both installed at the same time.
added this two lines in eclipse.ini
second line represents the jdk location of the javaw.exe file.
note: place -vm lines before -vmargs, otherwise default location is taken.
change the same as above in sts.ini
you need to check if your pc has a 64-bit or 32-bit operating system, then same goes for your jdk (64-bit/32-bit) and also for eclipse (64-bit/32-bit).
make sure they are all the same; if not, you need to download the one that matches your bitness.
look at the second line of the message box. there you can see which java runtime in fact is started. mine was suddenly c:\programdata\oracle\java\javapath\javaw.exe. this happened after i have installed a "chrome java updater" (chrome browser moaned: 'your java is outdated, you have to update...').
before this "chrome java update" my eclipse (luna jee x64) started without error. looking closer to the background i detected following: the chrome java updater (notabene started from an oracle site) added c:\programdata\oracle\java\javapath in front of the env var path. it contains three symbolic links to the newest java 8 jre installation in (x86) program folder -> hence to a 32 bit java jre. oracle replaces with java8 the old technique having the symlinks in system32 (64bit) resp. syswow64 (32bit).
meanwhile i learned. whatever java installer you have executed last (the *.exe) leads windows to remember that java flavour (32b or 64b), with the result that after an update the links in c:\programdata\oracle\java\javapath point to a java installation of the remembered flavour. if you have a 64b eclipse installation and encounter the described error: just re-install the newest 64b jdk. after that the java updates do no more link to a 32b version. and eclipse 64b will start correctly without the entry in eclipse.ini .
i had the same error when configuring eclipse.ini to use jre6. turns out i caused this error by incorrectly configuring eclipse to use the 64 bit jvm while running a 32 bit version of eclipse 3.7.
the correct configuration required the eclipse.ini -vm argumument to use "c:/program files (x86)/" instead of "c:/program files/".
make sure that the jvm version (32/64 bit) you use matches the eclipse version (32/64 bit).
- Cannot run Eclipse; JVM terminated with Exit code=13
- Cannot run Eclipse; JVM terminated. Exit code=13
- Error starting Eclipse on Ubuntu, JVM terminated Exit code=13
- Eclipse Birt JVM Terminated Exit code = -1
- Cannot run Eclipse; JVM terminated. Exit code=13 unlike others
- Eclipse error JVM terminated. Exit code=1 /usr/Java70/jre/bin/java
- Eclipse does not launch (Ubuntu) : JVM terminated. Exit code=13
- Cannot run Android project in Eclipse despite no errors
- Cannot run JavaFX 11 with Eclipse
- why I cannot use "run Android lint" from menu "Window" in Eclipse in toolbar I can run it, is it OK?
- Eclipse ADT Error: Cannot run program adb
- Cannot run as "PyDev: Django" in Eclipse
- Eclipse Crash on Launch - JVM terminated. Exit code=2
- Eclipse IDE fail to launch with JVM Terminated. Exit code=-1
- Eclipse does not launch (Ubuntu) : JVM terminated. Exit code=2
- Cannot run program "adb": error=2, No such file or directory while executing through eclipse
- eclipse IDE crashes after seconds with JVM terminated. Exit code=1
- Eclipse crash with error JVM terminated. Exit code=11
- My phone cannot be detected in eclipse to test run
- Cannot run a JUnit test case containing threads from Eclipse
- Does eclipse.exe run as JVM process? How does eclipse start?
- Eclipse terminated with exit value 0
- Cannot run server from eclipse with maven filtering application context
- Eclipse starting error of JVM terminated. Exit code=13 after upgrading Ubuntu updates
- JVM terminated with Exit Code 1 while accessing JFrame
- Cannot run "Hello World" program in Eclipse
- Eclipse doesn't start : JVM terminated. Exit code=14
- Eclipse IDE for C/C++ Linux Developers CANNOT run my java application
- JVM terminates with exit code 14 when trying to launch Eclipse
- Is it possible to specify a different JVM to run Eclipse with tycho-surefire-plugin
More Query from same tag
- Unable to update Integer field in SQLite database
- function sleep could not be resolved
- wso2 xpath expression in property mediator doesn't work
- How would I log every function call the PHP interpreter makes during a given script?
- AST eclipse, method call with arguments
- Content Assist not working in Eclipse for Android
- Eclipse unable to resolve plugin org.eclipse.wst.server.ui
- Commit failed: "Repository UUID '...' doesn't match expected UUID '...'" when committing to Google Code from Eclipse on Windows
- Rebuild eclipse editor
- Tomcat web apps location question
- how can I specify multiple runTargets in a single Pom when using gwt maven plugin
- Only changing the logo of special plugin
- Maven Build- error in eclipse build
- Subclipse: How to add the default output folder to version control (*.class files)?
- Exception regarding SLF4J
- I get a "Expected name at XX:YY" error on .json files in Eclipse. What is wrong?
- Eclipse debugger shows Hibernate-managed object has not been lazily-initialized
- Maven-Tycho Eclipse: Error installing plug-in built by Maven
- Android: Custom Action Bar Theme Error - (No Resource Found that Matches . . .)
- How do I put a folder with java files into eclipse's package explorer
- Cannot install Checkstyle plugin on Eclipse Mars
- Cyclic dependency in Eclipse CDT
- Best way to store Excel Rows with different columns related to each other?
- Openshift - ROOT.war deployed but no app
- How can I create a model/UML in Eclipse easily?
- Can't start Glassfish 18.104.22.168 on Eclipse Juno
- specified JRE installation does not exist (MacOSX)
- How to pass parameter as POST from BIRT Input parameter window
- Eclipse: Terminate current process before re-running