There are a few methods to get more information from this failure and troubleshoot the cause of the problem, but it’s actually worth trying a common solution to this problem first: reducing the Java heap size. In order to reduce the Java heap size, you need to add the -vmargs -Xmx512M options to Eclipse, which can either be done on the command line or by modifying the. The best way to fix this, assuming you do in fact have 64-bit JRE or JDK on your system, is to specify in eclipse.ini exactly which JVM you want it to use. Specifying the JVM path in eclipse.ini is strongly recommended because doing so isolates Eclipse from any potential changes to your system PATH that some program installers might make 2.4. Program Files is the folder where 64-bit Windows places 64-bit programs. This can happen when a system has more than one JVM installed, as is often the case on Windows 64-bit (for example, the JRE download page uses the bit-ness of the browser to determine what bit-ness download to offer you, and many people use(d) 32-bit browsers even though they run 64-bit Windows). Program Files (x86) is the folder where 64-bit Windows places 32-bit programs. First thing to check is whether you are using 32 or 64 bit version of Eclipse / Java. In this section we will try to find out the reason behind the error – ‘ Java was started but returned exit code=13‘. It’s often simplest to download a version of Eclipse that will work with whatever Java you already have installed.

64-bit Eclipse requires a 64-bit JVM, and 32-bit Eclipse requires 32-bit JVM–you can not mix-and-match between 32-bit and 64-bit, so make sure the version of Eclipse you installed matches the JVM/JDK that you’re using to run it (and make sure you’re using eclipse.ini to specify the exact JVM used to run Eclipse, described above).Īs a simple test, open a Command Prompt window, move to the directory that is pointed to by the -vm argument in your eclipse.ini, and run the intended java.exe with the -d32 switch to test if it supports 32-bit, or -d64 to test for 64-bit support. This is the most frequent cause of an Error 13. Plugins/.86_64_1.1.200.v20150204-1316Īnother common mistake on Microsoft Windows is a mismatch between the “bittedness” of Eclipse and the JVM/JDK.

The eclipse.ini file looks like something as below: ini file unless -launcher.appendVmargs is specified either in the. Any use of -vmargs on the command-line replaces all -vmargs settings in the. All lines after -vmargs are passed as arguments to the JVM, so all arguments and options for eclipse must be specified before -vmargs (just like when you use arguments on the command-line).

How to use eclipse ide for java 2019