MacOS 13.3 beta killed java [closed] - java

Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed yesterday.
This post was edited and submitted for review yesterday and failed to reopen the post:
Original close reason(s) were not resolved
Improve this question
I've been running OpenJDK & Apache Tomcat on my M1 MBAir - but with Ventura 13.3 I can't any longer...
% java --version
A fatal error has been detected by the Java Runtime Environment:
SIGBUS (0xa) at pc=0x00000001038e6f38, pid=1446, tid=8707
JRE version: (19.0.2) (build )
Java VM: OpenJDK 64-Bit Server VM (19.0.2, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, bsd-aarch64)
Problematic frame:
V [libjvm.dylib+0x3baf38] CodeHeap::allocate(unsigned long)+0x1c0
No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
I've tried brew uninstall openjdk, reboots, brew install java, reboots, etc... nothing.
Any thoughts?
UPDATE: For anyone else in a similar situation - I switched from “brew install java” to the Oracle .dmg and that solved my problem. Back to coding!

Related

Strange JVM Crash

A while ago I opened up my computer to work on a Minecraft mod I had been working on, but instead of running like normal, I got this exception:
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffbb88537e0, pid=18248, tid=9400
#
# JRE version: OpenJDK Runtime Environment Temurin-17.0.4.1+1 (17.0.4.1+1) (build 17.0.4.1+1)
# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.4.1+1 (17.0.4.1+1, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
# Problematic frame:
# C [atio6axx.dll+0x1937e0]
#
# No core dump will be written. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\Name\Desktop\SurvivalSnacks\run\hs_err_pid18248.log
#
# If you would like to submit a bug report, please visit:
# https://github.com/adoptium/adoptium-support/issues
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
After trying to find out what was happening for a few hours, I realized it wasn't a problem with my code. I tried running other java programs I had made. A simple Hello World program worked, but my LWJGL game crashed with the same exception, and any program that I used file IO crashed with File Not Found. The IO program also worked for other people that were working on the same project through GitHub.
The log from IntelliJ is too long to post in the question, so I used some website that posts text: https://jpst.it/2-biQ
Some things I tried:
Reinstalling IntelliJ
Reinstalling JDK
Running IntelliJ as admin
Factory Resetting my PC
All of the above things resulted in the same error
I also found this Stack overflow with a very similar problem to mine, but the solution did not work for me.
JVM Crash - "EXCEPTION_ACCESS_VIOLATION"
I fixed the problem by going to my graphics card company and downloading a version from before the error started happening. Just rolling back didn’t work because rolling back only let me go back one version, I had to go back to an update from 5 months ago.

A fatal error has been detected by the Java Runtime Environment in SafeFetchN with JavaFX on M1 Mac [duplicate]

Whenever I try to run my JavaFX problem I encounter a MacOS error, My code runs fine on other devices so I am not sure what is wrong.
Im using an M1 mac, with Java 17 and JavaFX up to the latest version. When running the JavaFX App, it opens up the gui for either 1 second or 30 seconds before crashing and spitting out the error provided. Any help would be greatly appreciated, and if you have other questions or need more info lmk.
I believe it's a problem with a /private/TMP folder or something with what I've seen online, but I can be completely wrong since that folder is basically empty right now so I don't see it being full or whatever.
If anyone can help or has any idea, I would really appreciate some feedback.
A fatal error has been detected by the Java Runtime Environment:
SIGBUS (0xa) at pc=0x000000010c0314f0, pid=1056, tid=28943
JRE version: Java(TM) SE Runtime Environment (17.0.1+12) (build 17.0.1+12-LTS-39)
Java VM: Java HotSpot(TM) 64-Bit Server VM (17.0.1+12-LTS-39, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, bsd-aarch64)
Problematic frame:
v ~StubRoutines::SafeFetchN
No core dump will be written. 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/peter/Desktop/BookStore/hs_err_pid1056.log
If you would like to submit a bug report, please visit:
https://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
Update your JavaFX version to the most recent available.
JavaFX bug reports mentioning:
stubroutines::SafeFetchN
are closed as duplicates of JDK-8275723, even though the crash error message there is slightly different.
Bug reports related to this are logged when trying to run early versions (less than 17.0.2) of JavaFX 17 on some M1 macs using the Monterey OS.
The linked case report recommends using JavaFX version 17.0.2 when it is released and notes a fix is also in the most recent JavaFX 18 early access releases, which are available for download.
Asker notes in comments:
I updated the JavaFx to 18 and it's all good
Another asker noted in comments on a duplicate:
I just tried to run the project with a JDK version 17.0.2 and it seems to work perfectly fine
I have a 17.0.2 one (newest version from Bellsoft Liberica).
Yes the issue is with JDK 17 Oracle. I have tried Azul Zulu JDK 17.34.19 and its working great! I am linking it below
Azul Zulu JDK 17 Download Page

How to install Matlab R2014a on Mac 10.9.4 (in fact, a Mac Virtual Machine)? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I try to install Matlab R2014a on Mac 10.9.4, which is a Virtual Machine in my Windows 7.
After open InstallForMacOSX.app, the logo things appear for a while, and then it says:
Install Matlab quit unexpectedly.
Problem details are:
Process: java [427]
Path: /tmp/*/java
Identifier: net.java.openjdk.cmd
Version: 1.0 (1.0)
Code Type: X86-64 (Native)
Parent Process: sh [389]
Responsible: sh [358]
User ID: 501
Date/Time: 2014-09-08 01:02:34.324 -0700
OS Version: Mac OS X 10.9.4 (13E28)
Report Version: 11
Anonymous UUID: 7FAD146F-0E07-23E8-AB07-4C6408874BB4
Crashed Thread: 19 Java: Java2D Queue Flusher
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
VM Regions Near 0:
-->
__TEXT 0000000103460000-0000000103471000 [ 68K] r-x/rwx SM=COW /tmp/*
Application Specific Information:
abort() called
...
In the log file, the report is :
A fatal error has been detected by the Java Runtime Environment:
SIGSEGV (0xb) at pc=0x00007fff8bdeefc8, pid=427, tid=40455
JRE version: 7.0_11-b21
Java VM: Java HotSpot(TM) 64-Bit Server VM (23.6-b04 mixed mode bsd-amd64 compressed oops)
Problematic frame:
C [libGL.dylib+0x1fc8] glGetString+0xf
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.
************************
Both of them are of a huge length. I'm sorry I'm not familiar with Java things. I wonder what is going on here? I already install Java SE and JavaforOSX.
I was having a similar problem installing R2014a on a Mac OS virtual machine. However, I got it working by doing something like this...
1) Download the latest java development kit from the oracle website here (It might work with the java runtime environment on it's own also, if you don't want the entire JDK)
2) Run the matlab installer from a terminal, specifying the location of the new JRE. See also JRE error when trying to install Matlab Compiler Runtime for more details, but the command for me (from within the MATLAB install directory) was
./install -javadir /Library/Java/JavaVirtualMachines/jdk1.8.0_20.jdk/Contents/Home/jre
At this point the installer worked basically as per normal, although there were errors with the Symbolic Math Toolbox, so I deleted the (faulty) installation, and ran the installer again as above, but without installing this toolbox.
3) Matlab didn't seem to open from the normal Applications shortcut, so I had to run it from a terminal and specify an alternative java virtual machine. See How to run Matlab from the command line? and this for more details. Note, you can export the MATLAB_JAVA environmental variable in your .bash_profile file, and you will need to restart/open a new terminal before the changes to your bash shell have an effect.
Good luck!

Aptana crashes on ubuntu linux

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

SIGSEGV 0xb on Java 1.6 and 1.7 on Ubuntu

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.

Categories

Resources