Minecraft Forums

ISSUE:

Every time I try to play Minecraft 1.9 it loads, launches Minecraft as a window with a black screen, and then Minecraft crashes and returns to the launcher, displaying the following under "Game Output":

[Client thread/INFO]: (Session ID is token:-:-)
[Client thread/INFO]: LWJGL Version: 2.9.4
[Client thread/INFO]: Reloading ResourceManager: Default
Game ended with bad state (exit code 139)
Ignoring visibility rule and showing launcher due to a game crash
Deleting /home/rich/.minecraft/versions/1.9/1.9-natives-5883769592210

My computer is really bad and runs Ubuntu Linux 10.04 :/

SOLUTION: Completely reinstall Minecraft and backup all saves you want to keep.

Quote from grimallq»

If you see a log named "Development Console" then you're using an extremely outdated launcher. Except that log looks like Game Output.

Make sure you have the latest launcher from Mojang and post Launcher log.

weird... http://hopper.minecraft.net/help/exit-code/code-139/

Quote from gerbil»

weird... http://hopper.minecraft.net/help/exit-code/code-139/

After reading that, my new theory is that 1.9 changed some requirement for playing and my computer is now too old to play Minecraft.
Any chance of that?

EDIT: System processor is Intel Centrino Duo, Graphics are OpenGL 2.0

# # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffc6a4f2177, pid=4660, tid=5924 # # 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+0x12177] # # 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\Brodie\AppData\Roaming\.minecraft\hs_err_pid4660.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 Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release

Quote from grimallq»

The didn't. Absolute minimum is still OpenGL 1.3. Though recommended minimum is OpenGL 2.1.

BUT

Opensource Linux drivers are ... less then optimal with proper OpenGL support. To say the least.

In the same exact way lousy Mac OSX drivers often mess up.

If I recall Ubuntu installs only Opensource MESA by default. Switch to vendor drivers.

Anything on the lowest version of Ubuntu installed? I have Ubuntu 10.04, is that too old?
Anyways, should I submit this as a bug to Mojang?

EDIT: EUREKA! I think I've figured out the problem. The hard part is figuring out how to solve it. Basically the last time I played Minecraft before this crash happened was in the afternoon, and then a power outage happened and my computer lost power and died.

I think that's why it says "Game ended with bad state (exit code 139)"

So my game is crashing because the last time it ended it ended badly.

How can I repair this....?

Quote from Gamerichie»

EDIT: EUREKA! I think I've figured out the problem. The hard part is figuring out how to solve it. Basically the last time I played Minecraft before this crash happened was in the afternoon, and then a power outage happened and my computer lost power and died.

I think that's why it says "Game ended with bad state (exit code 139)"

So my game is crashing because the last time it ended it ended badly.

How can I repair this....?

Quote from grimallq»

No. The way game ended previously has no effect on subsequent sessions.

Not unless you had such a catastrophic crash that game files were damaged. Which can happen during a powercut.

Reinstall the game from scratch, make backups of any saves you may want to keep.