Error starting Eclipse in Linux: "JVM terminated. Exit code=13" - linux

I am trying to run eclipse and encounter the errors. I am using Kubuntu as my OS and when I typed java -version in terminal I got 'java version "1.6.0_23"'. I have openJDK installed but I am not sure what can I do next. Any thoughts? Thanks.
ERROR:
JVM terminated. Exit code=13
/usr/bin/java
-Dosgi.requiredJavaVersion=1.5
-XX:MaxPermSize=256m
-Xms40m
-Xmx384m
-jar /home/lucky/Downloads/eclipse//plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar
-os linux
-ws gtk
-arch x86
-showsplash
- launcher /home/lucky/Downloads/eclipse/eclipse
-name Eclipse
--launcher.library /home/lucky/Downloads/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.1.2.R36x_v20101019_1345/eclipse_1310.so
-startup /home/lucky/Downloads/eclipse//plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar
-exitdata 5cf8058
-product org.eclipse.epp.package.php.product
-vm /usr/bin/java
-vmargs
-Dosgi.requiredJavaVersion=1.5
-XX:MaxPermSize=256m
-Xms40m
-Xmx384m
-jar /home/lucky/Downloads/eclipse//plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar
My eclipse.ini
-startup
plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.1.2.R36x_v20101019_1345
-product
org.eclipse.epp.package.php.product
--launcher.defaultAction
openFile
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vmargs
-Dosgi.requiredJavaVersion=1.5
-XX:MaxPermSize=256m
-Xms40m
-Xmx384m

Looking at the paths in the error it seems that you are not using eclipse from the ubuntu repositories (that's fine imo).
Check if the jvm is 64 or 32 bit. java -version will tell you. If you find this is a 64-bit jvm then go back to eclipse.org and download a eclipse version for 64-bit. You have eclipse for a 32-bit jvm. See your error message where it says -arch x86
Try to start eclipse from a shell using the -vm parameter. On ubuntu you can find the installed jre/jdk's under /var/lib/jvm/. E.g.:
./eclipse -vm /var/lib/jvm/sun-java6-jdk/bin
You could add this parameter to your eclipse.ini file.
Helps?
This could be of interest as well: Eclipse starting error of JVM terminated. Exit code=13 after upgrading Ubuntu updates

I have found solution for errors 13 and 1 in following video:
Eclipse Error 13 and Error 1
Both errors are fixed by editing eclipse.ini in eclipse directory.
Error 13 is fixed by adding complete path to javaw. In my case it is:
-vm
c:\Program Files\Java\jdk1.8.0_45\bin\javaw.exe
Error 1 is caused by setting arguments for virtual machine before setting vm. itself.
This means two lines we just added must be before the
-vmargs
line.
Done.

Specify the JVM you want to use in your eclipse.ini file, as described in http://wiki.eclipse.org/Eclipse.ini
I'd recommend using the JDK from Oracle; I'm not sure the current state of compatibility between Eclipse and OpenJDK.

This might sound a little odd but I have stumbled upon the same problem (StS 3.2.2 on Juno 4.2.2 with Java 7 u25 both 64 bit on win7) and nothing seemed to work, then I moved my sts out of the directory I originally installed it (d:#sts\springsource\sts-3.2.0.RELEASE) to (d:\springsource\sts-3.2.0.RELEASE), and now it works.
I kept it in both places and if I want to start it from its original location it promptly crashes with exit code 13, if I start it from the new place it works just fine.
So it might be that eclipse does not like hash marks, or it was "too far away" from root and some of the files paths-es went beyond 256 char. (Nonetheless its quite odd the get exit code 13 since in my case it had nothing to do with non-matching versions)

I had the same error.
I got through with the following:
which java
It gave me :/usr/local/java/jre1.7.0_25/bin/java
I went to the folder where eclipse was located (~/Developer/adt-bundle-linux-x86_64-20140624/eclipse/ in my case )
cd ~/Developer/adt-bundle-linux-x86_64-20140624/eclipse/
Then
./eclipse -vm /usr/local/java/jre1.7.0_25/bin
You can make this permanent by editing the eclipse.ini file:
Right after OpenFile I inserted 2 lines containing:
-vm
/usr/local/java/jre1.7.0_25/bin/java
The second line being the output from the which java command.
Now Eclipse loads for me but it misbehaves, hopefully not related.

I had this issue on my windows 8.1 machine. All the suggestions didn't fix my issue.
I then thought about the root cause. I believed it was caused by degrading from JDK-9 to JDK-8. I recently uninstalled JDK-9.
I went and checked the Environment Variable-->Path and it contained another Java reference of "C:\ProgramData\Oracle\Java\javapath".
I simply removed this extra "C:\ProgramData\Oracle\Java\javapath" from Path(environment variable), and My Eclipse worked.
I hope this helps others.

Related

How do I fix JavaFX runtime components are missing?

I have the following installed on Ubuntu 18.04.1 LTS:
openjdk version "10.0.2" 2018-07-17
OpenJDK Runtime Environment (build 10.0.2+13-Ubuntu-1ubuntu0.18.04.1)
OpenJDK 64-Bit Server VM (build 10.0.2+13-Ubuntu-1ubuntu0.18.04.1, mixed mode)
javafx.runtime.version=8.0.161
javafx.runtime.build=b00
However I try to run the sample java application that uses javafx I get the following error:
$ java -jar Untitled.jar
Error: JavaFX runtime components are missing, and are required to run this application
I have tried to run it in Eclipse, Intelli, and in the terminal with the same error.
I have set the classpath
:~$ echo $CLASSPATH
/usr/share/java/openjfx/jre/lib/ext/jfxrt.jar:.
I have copied all of the javafx files to the current directory.
I have tried everything I can find on the internet.
Does anyone know how to fix this?
On Ubuntu 18.04 with openjdk-11-jre and openjfx installed you could use:
% java --module-path /usr/share/openjfx/lib --add-modules ALL-MODULE-PATH \
-jar Untitled.jar
There is more information on how to run JavaFX programs at the openjfx.io site.

Android studio crashes

I am using android-studio in Arch linux 32bit from AUR.Recenty after latest pacman system upgrade , android-studio is refusing to start.Throws this error:
A fatal error has been detected by the Java Runtime Environment:
SIGSEGV (0xb) at pc=0x64056842, pid=645, tid=1686977344<br>
JRE version: Java(TM) SE Runtime Environment (7.0_72-b14) (build 1.7.0_72-b14)<br>
Java VM: Java HotSpot(TM) Server VM (24.72-b04 mixed mode linux-x86 )<br>
Problematic frame:<br>
C 0x64056842<br>
Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
An error report file with more information is saved as:
/home/joshua/java_error_in_STUDIO_645.log<br>
/usr/bin/android-studio: line 188: 645 Aborted (core dumped) LD_LIBRARY_PATH="$IDE_BIN_HOME:$LD_LIBRARY_PATH" "$JDK/bin/java" $AGENT "-Xbootclasspath/a:$IDE_HOME/lib/boot.jar" -classpath "$CLASSPATH" $VM_OPTIONS "-Djb.vmOptionsFile=$VM_OPTIONS_FILES_USED" "-XX:ErrorFile=$HOME/java_error_in_STUDIO_%p.log" -Djb.restart.code=88 -Didea.paths.selector=AndroidStudio1.4 $IDE_PROPERTIES_PROPERTY $IDE_JVM_ARGS $REQUIRED_JVM_ARGS $MAIN_CLASS_NAME "$#"
can anybody please suggest me how to fix this issue.Otherwise which package should I rollback so that it could work again?
Same here. I found this thread to be useful.
LD_PRELOAD=/lib/libglib-2.0.so studio.sh
However it seems like a workaround not a real solution.
EDIT:
Arch users:
wget http://pkgbuild.com/~heftig/glib2-2.46.0-2-x86_64.pkg.tar.xz
sudo pacman -U glib2-2.46.0-2-x86_64.pkg.tar.xz
Same error here!
Android studio 1.4.0.10-2
Arch linux
with jdk 8u60-1
EDIT:
Solved, after I changed the default java environments from java-8-jdk to java-8-openjdk.
A little late to respond to this post.I have similar problem with Android Studio 2.1.0 on linux OS (64 bit), studio crashing frequently . I tried to increase the size of JVM’s Heap by adding to gradle.properties file but it didn't help at all. I have updated java 1.8.0_77 to 1.8.0_92 now Android Studio works fine.

32-bit linux based eclipse giving error on startup in Fedora 12

I downloaded the 32-bit eclipse for my 32-bit fedora 12. I extracted the tar.gz without any error. But when i click on the eclipse executable, i am getting the error:
"Failed to load the JNI shared library "/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/../lib/i386/client/libjvm.so"
"
I am not able to resolve this error. Please inform how to proceed.
Regards,
Go to your eclipse folder
Open eclipse.ini file and check if there is -vm option set properly
Else set -vm in one line followed by your jdk installed bin folder.
Hope this helps yo solve your problem.
I'd suggest avoiding OpenJDK, as Eclipse will keep complaining about it.
So, navigate to http://java.com/en/download/manual.jsp and download appropriate Sun's Java package (32 or 64 bit, depending on your current installation). As Fedora uses RPMs for package management, I advise to use that method.
Then, after installation, run java -version in terminal, you should get something like:
$ java -version
java version "1.6.0_22"
Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
Java HotSpot(TM) Client VM (build 17.1-b03, mixed mode, sharing)

JRE (sun 1.6 21) crash with SIGBUS on Linux Debian 5

I have problems with JRE on Linux Debian 5.
JRE (sun 1.6 21) crash with SIGBUS on Debian 5 (kernel 2.6.26) during TEE-CLC java application execute.
TEE-CLC-10.1.0 is a java client application for Microsoft Team Foundation Server (TFS).
Here is the java virtul mashine command line:
exec java -Xmx512M -classpath
"$CLC_CLASSPATH" "-Dcom.microsoft.tfs.jni.native.base-directory=$BASE_DIRECTORY/native"
$RANDOM_DEVICE_PROPERTY com.microsoft.tfs.client.clc.vc.Main "$#"
When I try to execute the command (get files from server): tf get -r -force {branch_name} it start getting files and then minute or two later craches with the following error message:
A fatal error has been detected by the Java Runtime Environment:
SIGBUS (0x7) at pc=0xb77d3422, pid=29386, tid=3076802752
JRE version: 6.0_21-b06
Java VM: Java HotSpot(TM) Client VM (17.0-b16 mixed mode linux-x86 )
Problematic frame:
C [+0x422] __kernel_vsyscall+0xe
An error report file with more information is saved as:
/...../..../...../hs_err_pid29386.log
Segmentation fault.
I have about 900M free memory. I have checked limits: ulimit -a .
I have three other Linux Debian 5 computers and they works fine with the same settings.
I have checked everything . I don' t know why JRE don't work properly.
Does anybody have any idea how to handle it? What is wrong with JRE or with my Debian 5?
In my experience it is rare to get a faulty program to fail with a SIGBUS: error checking by compilers makes it hard to generate an odd memory address. The few times I've seen them recently was (IIRC) because I was using an incompatible shared library or .o file.
Is the LD_LIBRARY_PATH environment variable set for the executing program? If so, it might be causing the program to use an incorrect shared library.

m2eclipse crashes eclipse 3.5.SR2 running on openjdk-6-jdk

I downloaded the latest version of eclipse (3.5.SR2) and get m2eclipse installed on.
Instead of running on sun-jdk-6 (which is obsolete for the recent Ubuntu 10.04 alpha), I have eclipse running on open-jdk-6.
Everything was just fine. I can open my existing project and have them compiled as well as running tests.
However, with m2eclipse installed on, my eclipse will crash every time I start it.
If I stopped the m2eclipse plugin from contacting the central repo, then eclipse will continue to run normally.
The craziest point is that eclipse will exit immediately as soon as the contacting to central repo finish, but leave no track in the log.
What should I do right now?
Yeah, I was having the same problem. Was driving me crazy. (Ubuntu 10.04). I modified my eclipse.ini to be as follows (NOTE: I have /usr/lib/jvm/java-6-sun as a soft-link to /usr/lib/jvm/java-6-sun-1.6.0.20) - NOTE the "-vm" line and following line:
-startup
plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
-vm
/usr/lib/jvm/java-6-sun/bin/java
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.0.200.v20090519
-product
org.eclipse.epp.package.reporting.product
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
-vmargs
-Dosgi.requiredJavaVersion=1.5
-XX:MaxPermSize=256m
-Xms40m
-Xmx1024m
Now everything works great! Thanks all for the help!
confirming the exact same problem!
.. and the solution, using Sun JDK 1.6 Update 17 x64 eclipse runs fine now.
System:
Intel Core 2 Duo,
Ubuntu 10.04 x64
I created https://issues.sonatype.org/browse/MNGECLIPSE-2241 for this issue. As reported by running "eclipse -vm /usr/lib/jvm/java-6-sun/bin/java" instead.
Me too: running eclipse -vm /usr/lib/jvm/java-6-sun/bin/java once fixed the problem, and allowed Maven to update correctly. Since doing that, it seems that using openjdk is fine again.

Resources