The bug
Worlds aren't deleted after dying in hardcore mode.
How to reproduce
Die in hardcore mode
Click "Delete world"
→ This returns you instantly to the title screenClick "Singleplayer"
→ The world is still in the list
Opening the world will bring you back to the death screen, and produce a long list of the same error, repeated many times, in the Game Output tab in the launcher:
[06:05:34] [Client thread/FATAL]: Error executing task
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
This may happen because the world still appears to be loaded, even after returning to the title screen. Clicking the Options button will show the hardcore world in the background.
Also in the Game Output
you can see that the server was not stopped:
Game Output (15w47c)
## Deletion dialog ##
[22:36:35] [Server thread/INFO]: Saving chunks for level 'New World'/Overworld
[22:36:35] [Server thread/INFO]: Saving chunks for level 'New World'/Nether
[22:36:35] [Server thread/INFO]: Saving chunks for level 'New World'/The End
[22:37:24] [Client thread/ERROR]: Realms module missing
## Clicking on "Singleplayer" ##
[22:37:37] [Server thread/INFO]: Saving and pausing game...
[22:37:37] [Server thread/INFO]: Saving chunks for level 'New World'/Overworld
[22:37:37] [Server thread/INFO]: Saving chunks for level 'New World'/Nether
[22:37:37] [Server thread/INFO]: Saving chunks for level 'New World'/The End
## Entering world ##
[22:38:13] [Server thread/INFO]: Stopping server
[22:38:13] [Server thread/INFO]: Saving players
[22:38:13] [Server thread/INFO]: Saving worlds
[22:38:13] [Server thread/INFO]: Saving chunks for level 'New World'/Overworld
[22:38:13] [Server thread/WARN]: The save is being accessed from another location, aborting
[22:38:13] [Server thread/INFO]: Saving chunks for level 'New World'/Nether
[22:38:13] [Server thread/INFO]: Saving chunks for level 'New World'/The End
[22:38:13] [Server thread/INFO]: Starting integrated minecraft server version 15w47c
[22:38:13] [Server thread/INFO]: Generating keypair
[22:38:13] [Server thread/INFO]: Preparing start region for level 0
[22:38:14] [Server thread/INFO]: Preparing spawn area: 90%
[22:38:14] [Server thread/INFO]: Changing view distance to 8, from 10
[22:38:14] [Client thread/FATAL]: Error executing task
...
As you can see the "Delete" button does not cause the stopping of the server but instead the reopening of the world. Clicking the "Delete" button does not seem to do anything at all.
The reason
The following is based on decompiled version of Minecraft 1.8 using MCP. All method and class names are the names used in the decompiled version.
The reason why this happens is very likely that the client thread tries to save the world after the client was kicked, while the server tries to delete it at the same time.
Related issues
is duplicated by
relates to
Attachments
Comments


Can not reporduce. The delete world button does go to the "are you sure you want to quit" screen with the main menu and respawn buttons, but when I click respawn it says "you died. game over" and kicked me to the muliplayer screen. when I go back to the single player world options the world has been deleted.

I did not get the same error as you, yet I agree the hardcore delete world screen is very glitchy. I died in hardcore and tried to see if I could respawn by pressing the respawn button. When I did however it said that it was game over and I was kicked from the server. (I was playing single-player offline) and put me on the multiplayer server screen.
Edit: I tried this a few times on a modified superflat world (1 block of grass so i can break through and die 😛) Got the same result. Title screen and respawn should be changed to title and delete, the actual bug IMO is that the options were copied over from single player survival and that when you are playing single player offline it still sends you to the server select screen.

The basically just need to not have it come up. Its just cause they added the "are you sure" screen to the death screen so people wouldn't acidently hit main menu when they die.

I don't think the "Are you sure" screen should be removed because I think its a useful feature. (with the new "rebuild world" feature I can get the same world) I have accidentally deleted a world I wanted to rebuild or at least get the seed for the world a few times. (just cuz im used to pressing the respawn button in survival) It just needs to be tailored to fit hardcore mode too.

Video Proof: http://youtu.be/2jLoZtpa2PA
OS: Windows 7
Java: 7u40
Snapshot:13w39b

Confirmed for 1.7.2 and 1.7.4, please add to the list. Since I'm doing rapid successions of Hardcore Speed-Runs, my poor world list is getting FULL of "New World---------------" etc when this used to not be a problem!
Before, it was bad enough that clicking to return to the Main Menu instead brought you to a server list... but now, you either save and quit, or save and go to the server list! The "Delete World" button needs to do just that, then take us back to the main menu (not server list).
I sincerely hope this is fixed soon, it's getting super annoying having to go through and delete all these Hardcore Game Over worlds over and over and over and over...

Is this still a concern in the latest Minecraft version 14w30c? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

Just encountered this bug in 14w31a.
Though the respawn option lead to a crash (minecraft not responding).

Same here. There's a reddit post that just came out today (aug 5th 2014) that has people trying an extreme lava world on hardcore. I crashed my game trying the respawn button.

Confirmed for 14w32a

Please attach the complete output of the "Game Output" which can be found on the last tab of the launcher.
If the launcher closes after game start, please edit your profile and select "Launcher visibility" then, "Keep the launcher open"
Please also copy it after you pressed the "Delete" Button.

14w32b:
Clicking "Delete world" Button
[07:49:05] [Server thread/INFO]: user drowned
[07:49:05] [Client thread/INFO]: [CHAT] user drowned
[07:49:31] [Server thread/INFO]: Saving and pausing game...
[07:49:31] [Server thread/INFO]: Saving chunks for level 'B30646'/Overworld
[07:49:31] [Server thread/INFO]: Saving chunks for level 'B30646'/Nether
[07:49:31] [Server thread/INFO]: Saving chunks for level 'B30646'/The End
Then there are 2 options:
Clicking "Respawn" Button
[07:42:44] [Server thread/INFO]: user drowned
[07:42:44] [Client thread/INFO]: [CHAT] user drowned
[07:42:50] [Server thread/INFO]: Saving and pausing game...
[07:42:50] [Server thread/INFO]: Saving chunks for level 'B30646'/Overworld
[07:42:50] [Server thread/INFO]: Saving chunks for level 'B30646'/Nether
[07:42:50] [Server thread/INFO]: Saving chunks for level 'B30646'/The End
[07:42:52] [Server thread/INFO]: user lost connection: TextComponent{text='You have died. Game over, man, it's game over!', siblings=[], style=Style{hasParent=false, color=null, bold=null, italic=null, underlined=null, obfuscated=null, clickEvent=null, hoverEvent=null, insertion=null}}
[07:42:52] [Server thread/INFO]: user left the game
[07:42:52] [Server thread/INFO]: Stopping singleplayer server as player logged out
[07:42:52] [Server thread/INFO]: Deleting level B30646
[07:42:52] [Server thread/INFO]: Attempt 1...
After this, minecraft is not responding.
Clicking "Title Screen" button: This "works", you get to the title screen, but the world is not deleted:
[07:49:05] [Server thread/INFO]: user drowned
[07:49:05] [Client thread/INFO]: [CHAT] user drowned
[07:49:31] [Server thread/INFO]: Saving and pausing game...
[07:49:31] [Server thread/INFO]: Saving chunks for level 'B30646'/Overworld
[07:49:31] [Server thread/INFO]: Saving chunks for level 'B30646'/Nether
[07:49:31] [Server thread/INFO]: Saving chunks for level 'B30646'/The End
[07:51:15] [Server thread/INFO]: Stopping server
[07:51:15] [Server thread/INFO]: Saving players
[07:51:15] [Server thread/INFO]: Saving worlds
[07:51:15] [Server thread/INFO]: Saving chunks for level 'B30646'/Overworld
[07:51:15] [Server thread/INFO]: Saving chunks for level 'B30646'/Nether
[07:51:15] [Server thread/INFO]: Saving chunks for level 'B30646'/The End
If you press the "Title Screen" button and then re-enter the not-deleted hardcore-world, you are presented with your dead character and the "Delete world" Button (after wich you can again -> back to title screen -> world not deleted - or respawn -> crash).

I get a rather strange rather long winded message that I'm not seeing on other people's logs:
[18:08:17] [Server thread/ERROR]: Couldn't save chunk; already in use by another instance of Minecraft?
aqs: Failed to check session lock, aborting
at bqf.c(SourceFile:71) ~[14w32d.jar:?]
at aqn.I(SourceFile:2565) ~[14w32d.jar:?]
at bfr.a(SourceFile:107) ~[14w32d.jar:?]
at qq.b(SourceFile:160) [14w32d.jar:?]
at qq.d(SourceFile:231) [14w32d.jar:?]
at qr.c(SourceFile:185) [14w32d.jar:?]
at net.minecraft.server.MinecraftServer.y(SourceFile:598) [14w32d.jar:?]
...and so on. It actually has about 1000 entries, I'm assuming 1 for each chunk in a 16 chunk view radius (1089 chunks). This is after actually attempting to click on the blacked out "delete world" button the second time through. I have to actually click on the red x in the corner and tell windows "crash program rather than wait" before it will close, and no error report is generated (I got this from the log instead). As far as I can see it actually attempts to start the deletion but since I'm still using the chunks to exist in it counts it as 2 attempts to access it and the session lock is triggered.

Is this still a concern in the current Minecraft version 1.8.1 Prerelease 3 / Launcher version 1.5.3 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

I can confirm this for 1.8.1 and 1.8.1-pre2.

Oddly it seems to work with the beta Launcher 1.6.5 sort of. Clicking Respawn deletes the world but clicking back to title screen locks up the game. Will do more testing later.

Confirmed for
1.8.4 Now there is only the option "Delete world", however click this button only opens the main menu without you leaving the world (and doesn't even delete the world). You can see that when you try to create a new world, in the background there is still the hardcore world.

Confirmed for
1.8.5
1.8.6
Might relate to MC-78113
Bugs
World doesn't get deleted
Die in Hardcore mode
Click "Delete world"
Click "Singleplayer"
The world is still in the list
World stays open
Die in Hardcore mode
Click "Delete world"
Click "Singleplayer"
Click "Create New World"
You will see the Hardcore world in the background
Here are ramifications of that:
1. Entering another or the same world causes
[16:36:46] [Client thread/FATAL]: Error executing task
java.util.concurrent.ExecutionException: java.lang.NullPointerException
at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[?:1.8.0_25]
at java.util.concurrent.FutureTask.get(FutureTask.java:192) ~[?:1.8.0_25]
at g.a(SourceFile:61) [1.8.5.jar:?]
at ave.av(SourceFile:880) [1.8.5.jar:?]
at ave.a(SourceFile:325) [1.8.5.jar:?]
at net.minecraft.client.main.Main.main(SourceFile:124) [1.8.5.jar:?]
Caused by: java.lang.NullPointerException
at bcy.a(SourceFile:455) ~[1.8.5.jar:?]
at go.a(SourceFile:54) ~[1.8.5.jar:?]
at go.a(SourceFile:12) ~[1.8.5.jar:?]
at fh$1.run(SourceFile:13) ~[1.8.5.jar:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_25]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_25]
at g.a(SourceFile:60) ~[1.8.5.jar:?]
... 3 more
2. Deleting the world leads to
either a bunch of error messages in the launcher that it couldn't delete the world or when you delete it directly after pressing "Delete World", it says it deleted it but it will recreate it again as soon as you enter another world and creates some folders like the "region" and the "stats" folder
3. LAN mode
I am not sure if LAN mode even makes sense for Hardcore, because you still have the "Delete World" button then which seems to act differently because again the game doesn't delete the world but also after entering the world again there are the same circumstances like they were when the world was saved last
Leave this report open
I know you tend to close every single report which doesn't get confirmed every single version, but please can you let this report here open until the developers officially state that these bugs are fixed.
It really starts becoming embarrassing that one of the gamemodes is really bugged and the main functions aren't working and that for over 2 years already!

Confirmed in 1.9 snapshot 15w31c

Clicking the "Delete World" button fast enough in 15w31c allows the user to completely rejoin the world as if nothing had happened (per MC-83700).

Confirmed in 1.9 snapshot 15w33c

Confirmed in 1.9 snapshot 15w35e

Closing as invalid since players in hardcore are now put in spectator mode on death.

Turns out players still have the option to delete world. Reopening.

Confirmed for
15w41b It is still not closing the world properly

Gave the ticket to Marcono1234.

Confirmed for 15w47a

Confirmed for 15w49a. Attached another file to more clearly show how the menu screen backgrounds can be affected by this.

Does it affect 15w49b as well?

Confirm for 15w50a

u meant 15w50a

Yes, 15w50a, thanks.

Confirmed for 16w02a.

Confirmed for 16w03a.

Confirmed for 16w04a.

Confirmed for 16w05a.

Confirmed 16w05b.

Confirmed 16w07a.

Confirm for 1.9-pre1

Confirm for 1.9-pre2

Confirm for 1.9-pre3

Confirm for 1.9-pre4

Confirm for 1.9

Confirmed for 1.9.1-pre3.

Confirm for 16w14a

Confirm for 16w15a

Confirmed for 1.9.3-pre3.

Confirm for 1.9.4

Confirmed for 1.9.4.

Confirmed for 16w20a.

Confirmed for 16w21a.

Confirmed for 16w21b.

Confirmed for 1.10-pre1.

Confirmed for 1.10-pre2.

Confirmed for 1.10.

Confirmed for 1.10.1.

Confirmed for 1.11.2

Is it possible to move in this state? While on the title screen, it may be possible to get a game crash by getting memory to create chunks without a directory to save to.

@Th3F4114n0n3 I think it's either tick perfect or cpu clock perfect, which is why this is so rare

Can confirm for 1.12

Confirm for 17w50a

Affects 18w21a

Affects 1.13-pre1

1.13pre2

Affects 1.13-pre5

Affects 1.13-pre6

affects 18w31a

Confirmed for 1.13.1.

Confirmed for 1.13.2-pre2.

Still happening in 19w11b

As of 1.14, when you click delete world, the title background turns white.

Still an issue in 1.14.1

This bug still exists in 1.14.2 Pre-release 1

Confirmed for 1.14.4 pre4. Normal main menu though

Have this issue in Java 1.14.4 as well.
This issue will be fixed in 1.15. The fix is already available in the 1.15 development snapshots.


Aww, that's not really resolving it though, that's putting a band-aid on it. Having to manually delete the worlds is needlessly cumbersome. Why couldn't the button instead do what it said it would do, instead of being re-labeled to leave us with additional inconvenience? 😞

in Minecraft 1.6, clicking delete world after dying in a hardcore world actually deleted the world from disk. So to say that "return to the title menu" is always what the actual functionality of that button was, is wrong. In my opinion this should be marked "won't fix" instead of "fixed".