mojira.dev
MC-95128

Rare! Kill a mob = crashed game.

I walked over to a rabbit, killed, and out of nowhere, the game crashed. It's that simple. You'll find my OS in the crash report. (By the way, Apparently 1.8.8 isn't a released version.)

Description: Exception ticking world

java.lang.NullPointerException: Exception ticking world
	at aqu.a(SourceFile:40)
	at aqq.a(SourceFile:93)
	at aoa.a(SourceFile:440)
	at ld.a(SourceFile:174)
	at amy.a(SourceFile:857)
	at ld.c(SourceFile:104)
	at ld.d(SourceFile:116)
	at adm.a(SourceFile:277)
	at adm.f(SourceFile:273)
	at adm.p(SourceFile:658)
	at ahe.b(SourceFile:66)
	at afh.a(SourceFile:445)
	at le.h(SourceFile:383)
	at le.c(SourceFile:202)
	at net.minecraft.server.MinecraftServer.B(SourceFile:599)
	at net.minecraft.server.MinecraftServer.A(SourceFile:535)
	at bpo.A(SourceFile:152)
	at net.minecraft.server.MinecraftServer.run(SourceFile:451)
	at java.lang.Thread.run(Thread.java:745)

Attachments

Comments 10

1.8.8 is outdated, please update to 1.8.9.

It seems like I'm doing everything wrong...
First, I forget to turn on VBOs. Now, I'm using an outdated version and creating an issue about it.

Please attach the world and/or provide steps to reproduce the issue. Is the rabbit still alive? What happens if you try to kill it again?

Okay...
First off, the rabbit died as soon as I opened the world. I continued killing other mobs, but didn't get the same results. 2nd, I deleted the world because after playing on it, it became 'corrupt,' where the world kept crashing after opening it to LAN (which I have reported to Mojang), the only reason to play it. And finally, to reproduce, walk up to a rabbit (or who knows, any other mob might work, and could possibly only work in the snow biome), kill said mob (maybe getting a critical to finish it off), and there's a rare chance that the game will suddenly crash. Since I'm not an expert at these things (as you can tell by my description...), that's all I know.

This has nothing to do with the rabbit, just a coincidence. The crash is in the world generation.
Is this a custom world?

Apparently not...

Level seed: -414424123
Level generator: ID 00 - default, ver 1. Features enabled: true

Do you know at approximately what coordinates this happened?

Edit: Found some coordinates.

Player Count: 2 / 8; [lf['XxBrickBreakerxX'/4285, l='Survival of Shia Lebeouf', x=217.61, y=72.00, z=48.24], lf['LeapinLizardz'/480, l='Survival of Shia Lebeouf', x=93.97, y=67.48, z=-22.18]]

I just had the chance to test this bug:

  • Minecraft version 1.8.9

  • Render distance: 16 chunks

  • Teleported myself to 217, 72, 48; then to 93, 67, -22

  • Flew around for a bit

  • No crash

  • No rabbits found at all (via /say @e[type=Rabbit])

1.8.9 is outdated...

The world was generated in 1.8.8

Is this still an issue in the most recent versions (currently that is 1.10.2, or 16w42a) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time. If you are the owner/reporter of this ticket, you can modify the affected version(s) yourself.

Jacob Sammy Deaver

(Unassigned)

Unconfirmed

Minecraft 1.8.9

Retrieved