Minecraft Forums

I tried to play in the 15w39c snapshot, but loading up a world causes Java to crash for no apparent reason. This has not happened in any version before 15w39c. Here is the launcher log that was outputted:

Completely ignored arguments: [--nativeLauncherVersion, 286]
[17:12:02] [Client thread/INFO]: Setting user: Takoh__
[17:12:02] [Client thread/INFO]: (Session ID is token:27d88a24261946dfa3cc5091a5b19c3d:b83cb60eb83b4d63883241b6c09ed74a)
[17:12:04] [Client thread/INFO]: LWJGL Version: 2.9.4
[17:12:05] [Client thread/INFO]: Reloading ResourceManager: Default
[17:12:05] [Sound Library Loader/INFO]: Starting up SoundSystem...
[17:12:05] [Thread-5/INFO]: Initializing LWJGL OpenAL
[17:12:05] [Thread-5/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
[17:12:05] [Thread-5/INFO]: OpenAL initialized.
[17:12:05] [Sound Library Loader/INFO]: Sound engine started
[17:12:08] [Client thread/INFO]: Created: 512x512 textures-atlas
[17:12:11] [Server thread/INFO]: Starting integrated minecraft server version 15w39c
[17:12:11] [Server thread/INFO]: Generating keypair
[17:12:12] [Server thread/INFO]: Preparing start region for level 0
[17:12:13] [Server thread/INFO]: Takoh__[local:E:ed38b09c] logged in with entity id 0 at (-1237.5253402887918, 64.0, 1553.4809118746598)
[17:12:13] [Server thread/INFO]: §6Takoh__§r joined the game
[17:12:17] [Chunk Batcher 3/WARN]: Needed to grow BufferBuilder buffer: Old size 524288 bytes, new size 2621440 bytes.
[17:12:18] [Chunk Batcher 0/WARN]: Needed to grow BufferBuilder buffer: Old size 524288 bytes, new size 2621440 bytes.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffec2e1628c, pid=9104, tid=5260
#
# JRE version: Java(TM) SE Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [ig75icd64.dll+0x55628c]
#
# 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\Nicholas\AppData\Roaming\.minecraft\hs_err_pid9104.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.
#
AL lib: (EE) alc_cleanup: 1 device not closed

The error you are getting is most commonly caused by using a setting in a newer version of the game that does not exist in an older one or something along those lines. Easiest way to clear it would be to have Minecraft reinstall its local files. To do this you need to get to your ".minecraft" folder. You may only need to delete the options (options.txt) file then restart the game. Or you may need to delete everything in the .minecraft folder EXCEPT for the "saves" folder. Then once again, restart the game and it will re-download the files for you.

Quote from worndownkeys»

The error you are getting is most commonly caused by using a setting in a newer version of the game that does not exist in an older one or something along those lines. Easiest way to clear it would be to have Minecraft reinstall its local files. To do this you need to get to your ".minecraft" folder. You may only need to delete the options (options.txt) file then restart the game. Or you may need to delete everything in the .minecraft folder EXCEPT for the "saves" folder. Then once again, restart the game and it will re-download the files for you.

Ok, I have tried your solution by deleting the options.txt and the game resources, but that did not work. The issue is still happening.

EDIT: Tried playing in the latest stable release(1.8.8), and the game works correctly. There is no spazzing and big graphical glitches to be seen. Probably an issue with the snapshot itself?

Most likely an issue with the snapshot. The whole point of them is for testing, so crashes are sort of a good thing.

Quote from worndownkeys»

Most likely an issue with the snapshot. The whole point of them is for testing, so crashes are sort of a good thing.

Yeah, someone reported the same crash and issues on the Mojang Bug Tracker, but a Moderator marked it as "Invalid" claiming that it was a problem with their computer.

OK, so after messing around with the video settings, turning on VBOs made the glitch graphics go away. I turned VBOs off, and the glitch graphics came back. I am not sure why this is the case, but it fixed the problem, and I am happy about it.