![]() ![]() J 10.alcCreateContext(Lorg/lwjgl/openal/ALCdevice Ljava/nio/IntBuffer )Lorg/lwjgl/openal/ALCcontext +8 Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) We can further analyze the cause of the crash by looking at the stack trace. Looking at the problematic frame, we find that the crash happened in the OpenAL64.dll, a library that Minecraft uses to handle sounds. Searching further in the hs_err file, you should see the string “ See problematic frame for where to report the bug”, which suggests you should look further up in the file to pinpoint the problem. The crash happened outside the Java Virtual Machine Actually, just below the bug report link, if you see the message: “ The crash happened outside the Java Virtual Machine in native code”, it’s a clear sign that the crash was caused, not by the Java Virtual Machine, but rather some other piece of code, most likely a library of some kind. # Is it really the JVM that is crashing?īefore blaming the JVM, and filing a bug report on, you want to make sure it’s really the Java Runtime causing the crash. # See problematic frame for where to report the bug. ![]() # The crash happened outside the Java Virtual Machine in native code. # If you would like to submit a bug report, please visit: Minidumps are not enabled by default on client versions of Windows # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.172-b11 mixed mode windows-amd64 compressed oops) # A fatal error has been detected by the Java Runtime Environment: Below is an example of a crash that occured when running Minecraft. To find cues, you want to look in the generated hs_err file. There you are, relaxing and enjoying a game of Minecraft, and suddenly “ A fatal error has been detected by the Java Runtime Environment”!Ī fatal error can be caused by any Java application. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |