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.
Related
Currently I'm trying to read serial port. Working fine in Linux. But facing error in Windows machine.
I followed this link to read serial port and Downloaded RXTX library from here for windows machine (JAR + DLL file).
OS : Windows 10 with 64bit
Java jre : Jre 1.8.0_261 VERSION.
Exception throws when read through input stream.
Error log :
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000180005b00, pid=4508, tid=0x0000000000002b90
#
# JRE version: Java(TM) SE Runtime Environment (8.0_261-b12) (build 1.8.0_261-b12)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.261-b12 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [rxtxSerial.dll+0x5b00]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\user1\eclipse-workspace\serialport\hs_err_pid4508.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Suggessions will helpful for me. Thanks!
TL;DR: Do not use 1.8.0_261 use 1.8.0_251 instead
I tried to reproduce this error with 1.8.0_181, 1.8.0_251 and 1.8.0_261 using Windows 10.0 , 64 bit Build 18362 (10.0.18362.1082).
I could only reproduce this error with Jre 1.8.0_261. u181 and u251 worked fine for me. I would suggest to use java 8 u251 from https://www.oracle.com/java/technologies/javase/javase8u211-later-archive-downloads.html .
Serial port depending parts of the application I am working on failed today after the java update from 1.8.0_241 to 1.8.0_271. I think the problem could be the switch from Visual Studio 2010 to 2017 which Java 8 is build with now.
New Features:
➜ JDK/JRE Runtime Windows Visual Studio Library (DLL) Dependency Changes
Java 1.8.0_261 Release Notes
Update: I was on an quite old version(2017) of jssc(Java Simple Serial Connector). Unfortunately the original has no updates since a while. But I found a fork on GitHub which continues development. Whith the forked version I had no further issues!
I tested RXTX with the newer Java 8u281 release from 19 Jan. 2021 but it also crashes.
However AdoptOpenJDK 8u282 is working smoothly without any errors with the serial communication using RXTX and looks like it fully compatible with Oracle JDK!!! AdoptOpenJDK
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
I have the following setup:
Hadoop 1.2.1
Oracle Java 1.7
Suse Enterprise Server 10 32bit
If I execute the Pi-example in standalone mode with
bin/hadoop jar hadoop-examples-1.2.1.jar pi 10 10
then Java dies the hard way, telling me
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGFPE (0x8) at pc=0xb7efa20b, pid=9494, tid=3070639008
#
# JRE version: Java(TM) SE Runtime Environment (7.0_40-b43) (build 1.7.0_40-b43)
# Java VM: Java HotSpot(TM) Server VM (24.0-b56 mixed mode linux-x86 )
# Problematic frame:
# C [ld-linux.so.2+0x920b] do_lookup_x+0xab
#
# 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/hadoop-1.2.1-new/hs_err_pid9494.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.
#
(The full trace is here)
On a distributed setup, i can start-all components and they are ideling fine. But when I submit a job, then the jobtracker dies immediately with an java.io.EOFException, I assume this is due to the same error as above.
I have already tried the same hadoop on another computer, there everything is fine (altough this one runs Arch Linux 64bit), and other Javas (OpenJDK, 1.6, 1.7) don't help.
Any suggestions?
Probably Hadoop includes a native library that was either compiled for a different platform (e.g. 64 bit instead of 32 bit), or the library expects a different environment. The stack trace also shows that JVM_LoadLibrary() is trying to load a native lib.
Make sure you downloaded the correct version of Hadoop for your platform, or compile it yourself for your target platform.
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.
I have .jar file which during runtime reads one .dylib library which I compiled in OSX with GCC compiler.
Application runs without any problems on OSX 10.6.8.
Java version:
java version "1.6.0_33" Java(TM) SE Runtime Environment (build
1.6.0_33-b10-424-10M3720) Java HotSpot(TM) 64-Bit Server VM (build 20.8-b01-424, mixed mode)
GCC version:
i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc.
build 5658) (LLVM build 2336.1.00)
I use 64-bit Java and libs which .jar needs are compiled for x86_64. So, on Snow Leopard, everything runs fine.
I now switch my application to OSX 10.7.4. There I tried 2 different Java versions:
1st Java version (same as on Snow Leopard):
java version "1.6.0_33" Java(TM) SE Runtime Environment (build
1.6.0_33-b10-424-10M3720) Java HotSpot(TM) 64-Bit Server VM (build 20.8-b01-424, mixed mode)
2nd Java version (updated today):
java version "1.6.0_35" Java(TM) SE Runtime Environment (build
1.6.0_35-b10-428-11M3811) Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01-428, mixed mode)
GCC version:
i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc.
build 5658) (LLVM build 2336.9.00)
I first tried just to run application with .dylib compiled on Snow Leopard and I got this error:
Invalid memory access of location 0x0 rip=0x7fff894aa697 Segmentation fault: 11
And also new lines which didn't caused app to crash, but they don't show on Snow Leopard:
java[1366] <Error>: CGContextGetCTM: invalid context 0x0
java[1366] <Error>: CGContextSetBaseCTM: invalid context 0x0
java[1366] <Error>: CGContextGetCTM: invalid context 0x0
java[1366] <Error>: CGContextSetBaseCTM: invalid context 0x0
After this crash I tried to recompile dependency .dylib with GCC on Lion, but that changed nothing. I still get Segmentation fault: 11 error.
I read about this error on net and as far as I noticed it is very often on Lion since Java update may have messed something, but since I am not so familiar with Java - has anyone encountered these problems and if yes, is there a way to solve this?
Many thanks.
[edit #1: Attempt with Java 7 on OSX 10.7.4]
When running .jar with Java 7, crash occurs again, here's error report:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fff894aa697, pid=1471, tid=31503
#
# JRE version: 7.0_07-b10
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.3-b01 mixed mode bsd-amd64 compressed oops)
# Problematic frame:
# C [CoreFoundation+0x2a697] CFSetGetValue+0x17
#
# 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:
# /Users/username/Desktop/executable/hs_err_pid1471.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.
#
Abort trap: 6
With Mac OS X 10.8.2 and with Java 6 installation, problems disappeared. I was reading about this problem and read that there was some problems with Java 6 and Mac OS X 10.7.4. As far as I am concerned, I was just waiting to test application on 10.8.2 to check if it produces these errors only on 10.7.4 and it looks like those errors only occur on 10.7.4.
With an OS upgrade, problems are solved which is good enough answer for me in this case.
Best regards.
I ran into this today on OS X 10.8.2, so waiting for an update wasn't going to help. I was able to fix it by reinstalling Java for OS X.
I didn't bother trying to uninstall the messed up java, I just re-downloaded it an installed over it. This is the version I installed:
Java For OS X 10.8
If you're not on 10.8(Mountain Lion), then you probably need a different download. It can be found on the same site. Hopefully this helps someone.