mojira.dev
MC-80954

Mob Noises Stay After Hardcore World Death

Simple enough, a slime killed me on hardcore mode and I can still hear them. On the title screen. After deleting my world. While the Minecraft window is minimized.
How To Recreate:
1. Create a hardcore world (mine was a superflat)
2. Get killed by a mob that makes noise. (Like a spider or a zombie.)
3. Delete the world (on the worlds screen) then go to the main menu.
4. Minimize Minecraft.
You should still hear them.

Comments 9

Are they still reproducing the noise or is their sound just remaining?
I assume you mean the first, but that sounds completely illogical to me.

They're still reproducing it. The sounds aren't looping and I can hear the occasional... I don't really know what it is... basically, I also could hear something scurrying on the grass occasionally.

That's funny, I think that means the world persists in your RAM after the hardcore world death.
Could you attach console output?

I can confirm this: I dug myself into a deep cave containing lava, water, a zombie, and a skeleton. I allowed the zombie to slay me, and I can still here every single noise. (The noises being lava popping, water flowing, a zombie moaning, and a skeleton's bones clicking on the stone)
Interestingly enough, when swapping to the multiplayer menu, the sounds stop, and when switching back to the main menu, the sounds come back.
Even more interesting, when entering the options menu from the main menu, you can see your death screen as if you pressed escape ingame. There is no red overlay, nor buttons though.
You can also press escape on the options menu, and it will bring you back to your death screen, prompting that you delete the world. I pressed "delete world" yet it never deleted it oddly. I could head into the singleplayer menu and still open the world. Opening the world would sadly bring me back to the death screen.
After truly deleting the world via the singleplayer menu, I could still go back into "options" and revive it by pressing escape.
When creating a new world, it would, again, show my death screen through the menu.

I can't attach the output. 1. It's been deleted. 2. How do I even do that?

From the launcher menu, when the game is already loaded, go to the tab "Game Output".
After reproducing the bug, copy paste the whole log that has generated there to a plain text file and attach that to this post.

If you go to options screen in the game output in the launcher you can see:
[18:11:18] [Server thread/INFO]: Saving and pausing game...
[18:11:18] [Server thread/INFO]: Saving chunks for level 'Testing'/Overworld
[18:11:19] [Server thread/INFO]: Saving chunks for level 'Testing'/Nether
[18:11:19] [Server thread/INFO]: Saving chunks for level 'Testing'/The End

After reloading the world this is the only thing i can see in the console:
java.util.concurrent.ExecutionException: java.lang.NullPointerException
at java.util.concurrent.FutureTask.report(Unknown Source) ~[?:1.8.0_45]
at java.util.concurrent.FutureTask.get(Unknown Source) ~[?:1.8.0_45]
at g.a(SourceFile:61) [1.8.7.jar:?]
at ave.av(SourceFile:880) [1.8.7.jar:?]
at ave.a(SourceFile:325) [1.8.7.jar:?]
at net.minecraft.client.main.Main.main(SourceFile:124) [1.8.7.jar:?]
Caused by: java.lang.NullPointerException
at bcy.a(SourceFile:455) ~[1.8.7.jar:?]
at go.a(SourceFile:54) ~[1.8.7.jar:?]
at go.a(SourceFile:12) ~[1.8.7.jar:?]
at fh$1.run(SourceFile:13) ~[1.8.7.jar:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) ~[?:1.8.0_45]
at java.util.concurrent.FutureTask.run(Unknown Source) ~[?:1.8.0_45]
at g.a(SourceFile:60) ~[1.8.7.jar:?]
... 3 more
and its repeated about 1000 times.

Log:https://dl.dropboxusercontent.com/u/92370990/MC/latest.log

Does this issue still affect 1.8.7?

Ticket resolved as incomplete, because no answer in a reasonable amount of time (1+ year), if it still happens, please update the ticket.

Tyler Graham

(Unassigned)

Unconfirmed

Minecraft 1.8.6

Retrieved