I'm trying to export a game written in LibGDX, Java and Flixel-Android. The game was developed on a Mac, and runs on other Mac systems in Jar form. When running it on a Windows 7 machine it quits before completely starting up, and I get this dump:
A fatal error has been detected by the Java Runtime Environment:
EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x04a2b400, pid=5824,
tid=5912
JRE version: 7.0_09-b05 Java VM: Java HotSpot(TM) Client VM
(23.5-b02 mixed mode, sharing windows-x86 ) Problematic frame: C
0x04a2b400
Failed to write core dump. Minidumps are not enabled by default on
client versions of Windows
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 console window also prints "Execution protection violation" shortly before showing this, and then dumps the above into a text file as well. The text file includes a far, far longer dump that I won't post here unless people think necessary.
I have no idea what might be causing this, and I don't have much time to work it out! Anyone have any leads?
EDIT - I've narrowed it down to a section of code that loads a file from LibGDX's store. Is this a native library issue?
EDIT - It's somehow related to changing the size of a piece of text in Flixel-Android.
I would assume that the native library doesn't work properly on windows and/or with Java 7 (I know, this is quite obvious).
Bear in mind that Android's java is is java 1.5 compliant, so I could see that library breaking on java 7. I would verify which java versions are supported on the website of the library.
edit
It looks like java 7 is the culprit: http://code.google.com/p/libgdx/issues/detail?id=824 .
I think I'm an expert google user...
Related
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
I recently upgraded to Ubuntu 14.04. Since then Eclipse has been crashing. The message is
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x734be86d, pid=7930, tid=3076015872
#
# JRE version: Java(TM) SE Runtime Environment (8.0_05-b13) (build 1.8.0_05-b13)
# Java VM: Java HotSpot(TM) Client VM (25.5-b02 mixed mode linux-x86 )
# Problematic frame:
# C [libsoup-2.4.so.1+0x5486d] soup_session_feature_detach+0x1d
#
# 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/funcoding/Android Development/adt-bundle-linux-x86-20131030/eclipse/hs_err_pid7930.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.
#
Aborted (core dumped)
I also tried adding -Dorg.eclipse.swt.browser.DefaultType=mozilla" to eclipse.ini
Update: I tried many things but keeps on crashing unexpectedly. Finally I have decided to stick with Android Studio(Running smoothly as of now).
This is just a temporary fix, and I am sure it won't be selected as an answer, but I am putting this here so that anyone with this problem can at least continue to use eclipse until a better solution is found.
Tool tips appear to be causing the problem so I disabled them. I am able to continue programming and I haven't had it crash on me again (yet).
To disable tool tips go to Windows>Preferences>Java>Editor>Hovers and deselect all of the text hover key modifier preferences.
I hope this helps.
edit:
It also crashes when eclipse tries to content assist users. To disable this go to Windows>Preferences>Java>Editor>Content Assist. Scroll down to Auto Activation and disable auto activation
This bug has been reported here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=404776
Fix described in comments that works for me too is to add this line at the end of your eclipse.ini file
-Dorg.eclipse.swt.browser.DefaultType=mozilla
I am running Ubuntu 14.04 and was getting this with the Android ADT bundle of eclipse. Installing eclipse via the Ubuntu Software Center and then installing ADT via the directions linked below worked for me.
http://developer.android.com/sdk/installing/installing-adt.html
this is probably not the smartest solution but it definitely solved my problems:
after playing with eclipse.ini parameters I asked to a friend of mine to give me his eclipse.ini based on Kepler and I found out that some packages invoked in the startup were newer than the ones that come with the ADT bundle.
So I:
1) installed a fresh copy of Kepler
2) used the Android update site to add the android framework
3) after rebooting it asked me to update the Android SDK
So far I didn't have any crash (autocompletion etc.) so it seems it solved the problem...
hope that helps
Luca
You can reinstall eclipse.
I had got this problem after upgrading to 14.04. I downloaded the latest JRE, it didn't work.
Then I got the latest eclipse and now it works.
I have written a java program that plays videos using vlcj on a frame. I use NativeDiscovery().discover() to get the libvlc libraries, the program works on windows but on ubuntu NativeDiscovery().doscover() returns false and I get a fatal error with the log file: This is just the beginning of the log file
A fatal error has been detected by the Java Runtime Environment:
SIGSEGV (0xb) at pc=0xb7674f98, pid=21800, tid=2195979072
JRE version: 7.0_25-b30
Java VM: OpenJDK Server VM (23.7-b01 mixed mode linux-x86 )
Problematic frame:
C [libc.so.6+0x12ef98] _IO_file_underflow+0x68
Filed 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 include
instructions on how to reproduce the bug and visit:
https://bugs.launchpad.net/ubuntu/+source/openjdk-7/
Thanks guys for your help.
I had to face a bunch of similar errors as i worked with VLCJ last year. I dont know, if you have exactly the same error, as i had, but i can give you some hints:
in my case i had to use oracles java 7, not the openJDK
i had to set some symbolic links ("ln -s ...") to the vlc-executables, because the versionnumber was not the one, vlcj
expected.
I dont know, if this is useful to you, but as i was in your situation, i was grateful for every hint.
The reason could be the usage of the OpenJDK.
Try the OracleJDK.
This is almost certainly the same issue as https://github.com/caprica/vlcj/issues/62.
There is a long history of investigations into that issue which you can see in the comments at that github issue page.
The short version is that for some currently unknown reason:
a combination of 32-bit Java7 JVM and 32-bit Ubuntu triggers this fatal error;
the error pertains to the parsing of LUA scripts when VLC plays media;
deleting VLC's LUA scripts will resolve the problem - BUT things like YouTube will stop working (since VLC's YouTube support requires LUA);
It will work with Java6 on 32-bit Ubuntu;
It will work with Java7 on 64-bit Ubuntu;
If you write the equivalent "C" program, it will work - so something in the JVM is triggering the problem.
Unfortunately, I do not know if the bug is in Ubuntu's LUA build or the Oracle/OpenJDK build of the Java7 JVM.
Switching from OpenJDK to Oracle's JDK or vice versa will likely make no difference.
I encountered a similar problem. I solved it by removing openjdk and reinstalling it :)
In my case, installing Oracle JDK and setting up as default jdk has solved the problem.
At work, I am trying to install Matlab Distributed Computing Server R2011a on a Rocks CentOS Cluster. Following the instructions, I mount the ISO and run ./install &. The installer shows a splash screen but then crashes and outputs the error message below.
A fatal error has been detected by the Java Runtime Environment:
SIGSEGV (0xb) at pc=0x0000003d39471c7c, pid=29673, tid=1105340736
JRE version: 6.0_17-b04
Java VM: Java HotSpot(TM) 64-Bit Server VM (14.3-b01 mixed mode linux-amd64 )
Problematic frame:
C [libc.so.6+0x71c7c]
If you would like to submit a bug report, please visit:
http://java.sun.com/webapps/bugreport/crash.jsp
My boss and I found an article at http://greg.porter.name/wiki/HowTo:MatlabOnRocks by someone who has the exact same problem, but never figured out how to fix it. Has anyone else encountered this problem? If anyone has found a fix, I would be very interested in knowing what steps you took to fix this problem.
Sounds like a "try to run things on an unsupported platform"-issue.
In this kind of problems, ensure that you do this on a platform explicitly stated to support this combination. I do not believe that CentOS is a supported Oracle JVM platform.
It seem to be a general problem of java on memory limits set by cluster manager.
We are encounter this problem with SGE on Fedora Core 13.
see bug on fedora
Solution is to set limits to ~ 4 Go (not easy all the time ...)
or set environment
Anyone have GWT 1.6.4 running on FreeBSD? Our build server is a FreeBSD box, and dies with the following when we try to compile:
# An unexpected error has been detected by Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x0000000800d0c724, pid=4749[thread 34370233088 also had an error], tid=0xa02d80
#
# Java VM: Diablo Java HotSpot(TM) 64-Bit Server VM (10.0-b23 mixed mode bsd-amd64)
# Problematic frame:
# V [libjvm.so+0x20c724]
#
# An error report file with more information is saved as:
# /usr/home/username/reporting/hs_err_pid4749.log
#
# Please submit bug reports to freebsd-java#FreeBSD.org
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
Interestingly, Maven seems to include gwt-dev-1.6.4-linux.jar in the classpath, presumably because there is no version for FreeBSD; I don't know if this is related or not. We are just trying to compile, not use hosted mode, so I don't believe any native libraries are actually required. This used to work fine for us with GWT 1.5.
If you search Google for that frame (libjvm.so+0x20c724) you find some relevant recent threads on the freebsd-java list.
Looks like the problem might be related to IPv6? The solution proposed there was to add
-Djava.net.preferIPv6Addresses=false
-Djava.net.preferIPv4Stack=true
to the configuration.
It's unusual to see a FreeBSD build system for java; there isn't a lot of flexibility or support for Java on that platform. Is your product deployed on FreeBSD as well? If the solution above doesn't work, you may have to get more closely engaged with the freebsd-java community or else consider trying another platform for the build.
We seem to have dodged this by using JDK5 to compile our GWT-based code. Not a perfect solution, but a work-around.