I am using eclipse 3.7 (indigo) and it crashes every time i try to get the auto suggestion by pressing Ctrl+Space. I have even tried to change my eclipse and jdk version, but still getting the same error.
I am running on Ubuntu 13.04 and when i tried to run eclipse from terminal i got the following error -
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f4d744f2009, pid=21632, tid=139972060423936
#
# JRE version: 7.0_21-b02
# Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libsoup-2.4.so.1+0x6e009] soup_session_feature_detach+0x19
#
# 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/swapnilg/hs_err_pid21632.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# https://bugs.launchpad.net/ubuntu/+source/openjdk-7/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Here is the log file that i got. Please help me.
it seems like there is bug 404776 in eclipse causing this. I had this effect on Fedora 19 with Eclipse Juno and Kepler. Problem is caused by newer version of libsoup.
There is a workaround which worked pretty well for me, just add
-Dorg.eclipse.swt.browser.DefaultType=mozilla
at the end of your eclipse.ini
BR,
Alex
What Java versions have you tried? OpenJDK and? Did you consider using the Oracle's one?
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java7-installer
sudo update-java-alternatives -s java-7-oracle
java -version
Do you really need Indigo (3.7)? We have Juno (4.2) now... ooops Kepler (4.3) is just out.
Related
I faced an fetal error with eclipse ide, when i try to open eclipse load GUI and then close, that occur each time opened eclipse ide.
Error Loading DDMS Preferences
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f5a0c9822a1, pid=4316, tid=140027354994432
#
# JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build 1.7.0_45-b18)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libsoup-2.4.so.1+0x6c2a1] soup_session_feature_detach+0x11
#
# 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:
# /opt/eclipse/hs_err_pid4316.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug
Work around
change eclipse owwner.
run eclipse as root.
Extract jdk again on /opt.
Made link to jre from /opt to /usr/bin.
But problem still exists, any help will be appreciated.
Based on this my problem had been solved.
For a workaround add the following to the end of your eclipse.ini
-Dorg.eclipse.swt.browser.DefaultType=mozilla
If
-Dorg.eclipse.swt.browser.DefaultType=mozilla
doesn't work and your OS is debian, try solution in this post:
http://forums.debian.net/viewtopic.php?f=8&t=115477
I'm using java version "1.7.0_45" with eclipse kepler and on server startup I'm getting the below error log.
Although I've found several posts[1, 2] regarding the same issue, I've tried everything from adding -Dorg.eclipse.swt.browser.DefaultType=mozilla, -XX:LoopUnrollLimit=1 and ulimit -c unlimited but nothing worked for me.
Is there any other work around ?
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x0000000000000000, pid=7084, tid=139749936641792
#
# JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build 1.7.0_45-b18)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C 0x0000000000000000
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
#
SIGSEV means that your program is producing a so called segmentation fault. Writing over array boundaries, OR invalid memory addresses, etc... So I think you have to re install eclipse first and then see if you have to reinstall java and eclipse both... if the first wont work for you.
I am not sure if this is the correct guess, I hope no one downvotes this...
I had a similar error while I started netbeans in Ubuntu 13.04. I fixed it with
sudo apt-get install openjdk-7-jdk
Try and see if it works.
Every time i open Aptana it crashes.
A fatal error has been detected by the Java Runtime Environment:
SIGSEGV (0xb) at pc=0x00007f14294b2c91, pid=5722, tid=139727004391168
JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build 1.7.0_45-b18)
Java VM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops)
Problematic frame:
C [libsoup-2.4.so.1+0x6ac91] soup_session_feature_detach+0x11
Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
If you would like to submit a bug report, please visit:
http://bugreport.sun.com/bugreport/crash.jsp
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.
It happend to me after upgrade to ubuntu 14.04 using Oracle Java 7. In the Aptana folder there are hs_err_pid...log. Opening the last one of them I saw:
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
so, I did open a terminal and I worte directly:
ulimit -c unlimited
and it worked for me. No problems until now.
It looks like you have a broken installation of Aptana, either caused by a bug in the Eclipse / Aptana codebase, or some incompatibility with your Ubuntu installation.
If this was working before, try and find out what has changed recently. (Did you install new plugins? Did you apply some Ubuntu patches? Did you update versions of your OS or Aptana?)
If it never worked, check to see if your combination of Aptana and the OS are supported.
Either way, the most likely solution is going to be to reinstall, upgrade or downgrade something to get rid of the apparent incompatibility.
For the record, I suspect that this is related to the following Eclipse bug:
crash: fatal error in soup_session_feature_detach with WebKitGTK+ >= 1.11.91
libsoup2.4-1: Problem with Eclipse and java
Quoting from http://www.webupd8.org/2014/05/fix-aptana-studio-3-crashing-in-ubuntu.html :
In the folder where you've extracted / install Aptana Studio 3, you should have a file called "AptanaStudio3.ini" - open this file with a text editor and at the end of the file, add this line:
-Dorg.eclipse.swt.browser.DefaultType=mozilla
From what i gathered around the internet, it seems to be a problem with webkit, what did the trick for me was removing the library:
apt-get purge libwebkitgtk-1.0-common
The problem is, other programs like the gimp use that library...
Or you may turn off the contextual help like guyfromfl suggested here
today my Eclipse continue crashing and show me this message:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f9d6dfd4c91, pid=5739, tid=140316573566720
#
# JRE version: 7.0_25-b30
# Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 )
# Problematic frame:
# C [libsoup-2.4.so.1+0x6ac91] soup_session_feature_detach+0x11
#
# Core dump written. Default location: /home/panthe/eclipse/core or core.5739
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# https://bugs.launchpad.net/ubuntu/+source/openjdk-7/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Someone can help me?
Check bug report https://bugs.eclipse.org/bugs/show_bug.cgi?id=404776 . I suggest you to upgrade to the newest Eclipse 4.3 (Kepler).
Alternativelly you can try workaround suggested in comment #6:
For a workaround add the following to the end of your eclipse.ini
-Dorg.eclipse.swt.browser.DefaultType=mozilla
Upgrade to 4.3 or 4.4 works better, since for some Eclipse projects it continues to crash (egit, ADT...). If you are running old version of Eclipse I suggest you to delete the old installation and reinstall new version of Eclipse.
Install latest Eclipse in Ubuntu 14.04
I have really annoying problems with Java 1.6 and Java 1.7 on Ubuntu 13.10 (and Xubuntu 12.10), both x64. My problem doesn't occur on Debian 6.0 x64.
I run some test code for a nodejs application running Java code per JNI (if I understand it correctly, I'm not the developer of the code). The developers said, that it worked with no problems on their systems.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f0aef63e2fb, pid=3442, tid=139685052057408
#
# JRE version: 7.0_21-b11
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.21-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V [libjvm.so+0x5842fb] JNI_ArgumentPusherVaArg::JNI_ArgumentPusherVaArg(_jmethodID*, __va_list_tag*)+0x1b
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
#
Full log is on pastebin: http://pastebin.com/bexYiHHJ
I am using VMWare Workstation 9.0.2 to virtualize Ubuntu 13.10 x64, Xubuntu 12.10 x64 and Debian 6.0. I get the same error with Java 1.6. I also tried the OPENJDK Java. It works completly fine under Debian 6.0 with kernel 2.8 but doesn't work on Ubuntu 13.10 and Xubuntu (here are kernels 3.5 and 3.8, but should this really matter?).
What can I do now? I searched a lot in the internet and this board here. Sometimes it was defected hardware but I virtualize here and it works on Debian. Some others said to add some parameters but I don't really know where to add these parameters because I don't run Java from the command line, it will automatically started in the Node.JS Application.
Please Help!
I have the similar problem and it was solved with this java parameter: -XX:-UseCompressedOops
I don't know what the problem was, but I switched to a Debian 7 Version with Kernel 3.2 as work system. First, I had the same problem but then I installed a basic installation and download the precompiled node.js application. Maybe in my GCC was something wrong, I don't know.
If someone had the same problem and got a solution, it would be nice to know what the cause was.