Skip to content
Advertisement

After update linux to version 4.2, Java write “Failed to write core dump”?

I work on one programm, that need to java 7. But when I update archlinux to 4.2 (from 4.1) ,when I start the programm, java write me:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fdf76d41be0, pid=3512, tid=140597796308736
#
# JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 1.7.0_79-b15)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  0x00007fdf76d41be0
#
# 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/nozdrin/workspace/rvec/server/bin/hs_err_pid3512.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#

Java not update!! What happend with java and what do I need?

EDIT:

I found, when start the programm, he added keys -J-XX:PermSize=200m -J-XX:MaxPermSize=256m. When I delete this keys, java return another error:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f164f6b0be0, pid=5145, tid=139733914535680
#
# JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 1.7.0_79-b15)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  0x00007f164f6b0be0
#
# Core dump written. Default location: /home/nozdrin/workspace/rvec/server/bin/core or core.5145
#
# An error report file with more information is saved as:
# /home/nozdrin/workspace/rvec/server/bin/hs_err_pid5145.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#

This errors appeared when I update linux. I tried return old linux 4.1, but error still.

File hs_err_pid5145.log – is link on Google Drive.

Advertisement

Answer

Problem solved when I update to 4.4 kernel! Thank all!

User contributions licensed under: CC BY-SA
4 People found this is helpful
Advertisement