Game freeze after closing an "Open to LAN" single player world
The bug
When the host of a singleplayer world which was opened to LAN tries to close the world their game (client) may freeze.
The log shows that the server was successfully stopped though.
[17:42:54] [Server thread/INFO]: BartZeroSix left the game [17:42:54] [Server thread/INFO]: Stopping singleplayer server as player logged out [17:42:54] [Server thread/INFO]: Stopping server [17:42:54] [Server thread/INFO]: Saving players [17:42:54] [Server thread/INFO]: Saving worlds [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/Overworld [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/Nether [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/The End
How to reproduce
- Open a world
- Open it to LAN
- Try to close the world
Note: Since this bug seems to be caused by a race condition it could be possible that you cannot reproduce this bug with some computers.
Code analysis and debugging results
JStack, WhatIsHang, and debug logs related to this issue
This bug seems to have the same cause like MC-92255, which is caused by the method IntegratedServer.initiateShutdown being called twice.
Environment
Windows Vista. Java version 7 update 67.
OS X 10.10.3 Java 8u45
Linked Issues
is duplicated by36
MC-65329LAN - Game freezes on hosting player after save & quit.DuplicateMC-66533Saving game bugDuplicateMC-66646When singleplayer world is open to LAN, pressing "Save and Quit to Title" crashes game without crash report.DuplicateMC-66657Lan +LogoutDuplicateMC-67130Game Freeze DuplicateMC-71357Game Freezes when trying to save worldDuplicateMC-71850Minecraft gets stuck on menu screen with the button "Save and quit to title''DuplicateMC-71911Save and Quit to Title keeps hangingDuplicateMC-72742Hang on "Save and Quit to Title" on OSX 10.9.5 after Open to LANDuplicateMC-73057Client sometimes hangs when doing save and quit on a world opened to LAN.DuplicateMC-73366Game crashes when i click 'save and quit'.DuplicateMC-74947Window doesn't always close when you click save and quit to titleDuplicateMC-76043Minecraft freezes after closing LAN worldDuplicateMC-77580App hang when pressing "Save and Back to Main Menu"DuplicateMC-78850Game freezes on "Save and Quit to Title" after playing in Lan Single playerDuplicateMC-78892Game freezes after "Save and Quit to title" [Updated]DuplicateMC-82036halt when quiting a LAN worldDuplicateMC-84038LAN server crashes when exiting worldDuplicateMC-84546Game becomes unresponsive whilst quitting with an open LANDuplicateMC-92188Save Game ErrorDuplicateMC-98597Crash/Freeze when logging out of Single player worldDuplicateMC-98897Game freezes when closing LAN world DuplicateMC-98929Freeze during world savingDuplicateMC-103679Crash on 'Save and Quit'ing LAN as HostDuplicateMC-111315World freezing / breakingDuplicateMC-112606Game Crashes after you play on LAN worldDuplicateMC-116554When I try to save and quit to title in snapshot 17w16b my game crashesDuplicateMC-116634When exiting a lan world as host the game freezes DuplicateMC-118673Minecraft freezes after saving and quoting a single player game that was opened to LANDuplicateMC-118742Crash while saving local gameDuplicateMC-118795Open to LAN Java SE crashDuplicateMC-119137Crash for host when LANDuplicateMC-119817Save and Quit Crashing ErrorDuplicateMC-124824Crash when closing LAN world.DuplicateMC-127621Minecraft crashes when quiting to menu when Open to LAN is enabledDuplicateMC-131179Application Lock Up on Save and QuitDuplicate
![[Mod] Pokechu22](../../../data/avatars/users/92931.png){kind=small}
- Fixed
Bart Mons![[Mojang] Cory Scheviak](../../../data/avatars/users/92893.png)
[Mojang] Cory Scheviak- 87
- 49
- Confirmed
- closing freezing lan singleplayer
1.8 - 1.13-pre3
1.8 1.8.1-pre1 1.8.1-pre2 1.8.1-pre4 1.8.1 1.8.2-pre6 1.8.3 1.8.4 1.8.5 1.8.7 1.8.8 15w31a 15w40b 15w41b 15w45a 15w46a 15w47a 1.8.9 15w50a 16w02a 16w03a 16w04a 16w05a 16w05b 1.9-pre1 1.9-pre2 1.9-pre3 1.9-pre4 1.9 1.9.1 1.9.2 16w14a 16w15a 1.9.4 16w20a 1.10 1.10.2 16w32b 16w39a 16w43a 16w44a 1.11-pre1 1.11 16w50a 1.11.1 1.11.2 17w06a 17w13a 17w13b 17w14a 17w15a 17w16a 17w16b 17w17b 17w18a 17w18b 1.12-pre1 1.12-pre2 1.12-pre3 1.12-pre4 1.12-pre5 1.12-pre6 1.12-pre7 1.12 17w31a 1.12.1-pre1 1.12.1 1.12.2-pre1 1.12.2-pre2 1.12.2 17w43a 17w43b 17w45a 17w45b 17w46a 17w47a 17w47b 17w48a 17w50a 18w20a 1.13-pre1 1.13-pre3- 18w01a 1.13-pre6
Created Issue:
Game crash after closing a single player world if he is "Open to LAN"
That bug appends only if the world is "open to LAN", since release 1.8.
That world was created in 1.8 too.When i press Echap and click "Save and quit to title", Minecraft freeze. I have to shut it down, then an error message pop saying "Java(SE) binary does not respond".
After that the launcher appear with bug informations on it.It does not append every time, but around 1 out of 3 times.
Here is what is write in the launcher :
[17:42:54] [Server thread/INFO]: BartZeroSix lost connection: TextComponent{text='Disconnected', siblings=[], style=Style{hasParent=false, color=null, bold=null, italic=null, underlined=null, obfuscated=null, clickEvent=null, hoverEvent=null, insertion=null}}
[17:42:54] [Server thread/INFO]: BartZeroSix left the game
[17:42:54] [Server thread/INFO]: Stopping singleplayer server as player logged out
[17:42:54] [Server thread/INFO]: Stopping server
[17:42:54] [Server thread/INFO]: Saving players
[17:42:54] [Server thread/INFO]: Saving worlds
[17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/Overworld
[17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/Nether
[17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/The EndEnvironment
Windows Vista. Java version 7 update 67.
Gamecrashafter closing a single player worldif he is "Open to LAN"Game freeze after closing an "Open to LAN" single player world
is duplicated by
That bug appends only if the world is "open to LAN", since release 1.8.
That world was created in 1.8 too.When i press Echap and click "Save and quit to title", Minecraft freeze. I have to shut it down, then an error message pop saying "Java(SE) binary does not respond".
After that the launcher appear with bug informations on it.It does not append every time, but around 1 out of 3 times.
Here is what is write in the launcher :
[17:42:54] [Server thread/INFO]: BartZeroSix lost connection: TextComponent{text='Disconnected', siblings=[], style=Style{hasParent=false, color=null, bold=null, italic=null, underlined=null, obfuscated=null, clickEvent=null, hoverEvent=null, insertion=null}}[17:42:54] [Server thread/INFO]: BartZeroSix left the game
[17:42:54] [Server thread/INFO]: Stopping singleplayer server as player logged out
[17:42:54] [Server thread/INFO]: Stopping server
[17:42:54] [Server thread/INFO]: Saving players
[17:42:54] [Server thread/INFO]: Saving worlds
[17:42:54][Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/Overworld[17:42:54][Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/Nether[17:42:54][Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/The EndThat bug appends only if the world is "open to LAN", since release 1.8.
That world was created in 1.8 too.When i press Echap and click "Save and quit to title", Minecraft freeze. I have to shut it down, then an error message pop saying "Java(SE) binary does not respond".
After that the launcher appear with bug informations on it.It does not append every time, but around 1 out of 3 times.
Here is what is write in the launcher :
[17:42:54] [Server thread/INFO]: BartZeroSix lost connection: TextComponent{text='Disconnected', siblings=[], style=Style{hasParent=false, color=null, bold=null, italic=null, underlined=null, obfuscated=null, clickEvent=null, hoverEvent=null, insertion=null}} [17:42:54] [Server thread/INFO]: BartZeroSix left the game [17:42:54] [Server thread/INFO]: Stopping singleplayer server as player logged out [17:42:54] [Server thread/INFO]: Stopping server [17:42:54] [Server thread/INFO]: Saving players [17:42:54] [Server thread/INFO]: Saving worlds [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/Overworld [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/Nether [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/The End
From
MC-73057:Sometimes when opening a world to LAN the client will hang and require force quit when choosing "Save and Quit to Title".
This does not happen every time but rather once or twice out of 3-10 times trying it but sometimes more often.
Step to recreate:
Create new single player world all default settings.
Hit escape and click "Open to LAN"
Turn "Allow Cheats" to ON
Click "Start LAN World"
Explore the world for a few minutes
Hit Escape key and choose "Save and Quit to Title"
Repeat couple or so times until in hangs if neededTo me it acts like the network stream is not being closed every time.
NOTE: Upon force quitting the client the launcher does reappear with the Game Output tab selected but there are no errors.
relates to
relates to
relates to
is duplicated by
Any mod can do a simple skim down the main activity feed and link them.
Windows Vista. Java version 7 update 67.
Windows Vista. Java version 7 update 67.
OS X 10.10.3 Java 8u45
relates to
is duplicated by
![[Mod] Torabi](../../../data/assets/gravatar/torabi.png){kind=small}
is duplicated by
is duplicated by
is duplicated by
relates to
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Confirmed for 1.10, it seems to be worse than it used to be. D: I really wish this would be fixed!
That bug appends only if the world is "open to LAN", since release 1.8.
That world was created in 1.8 too.When i press Echap and click "Save and quit to title", Minecraft freeze. I have to shut it down, then an error message pop saying "Java(SE) binary does not respond".
After that the launcher appear with bug informations on it.It does not append every time, but around 1 out of 3 times.
Here is what is write in the launcher :
[17:42:54] [Server thread/INFO]: BartZeroSix lost connection: TextComponent{text='Disconnected', siblings=[], style=Style{hasParent=false, color=null, bold=null, italic=null, underlined=null, obfuscated=null, clickEvent=null, hoverEvent=null, insertion=null}} [17:42:54] [Server thread/INFO]: BartZeroSix left the game [17:42:54] [Server thread/INFO]: Stopping singleplayer server as player logged out [17:42:54] [Server thread/INFO]: Stopping server [17:42:54] [Server thread/INFO]: Saving players [17:42:54] [Server thread/INFO]: Saving worlds [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/Overworld [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/Nether [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/The End
From
MC-73057:Sometimes when opening a world to LAN the client will hang and require force quit when choosing "Save and Quit to Title".
This does not happen every time but rather once or twice out of 3-10 times trying it but sometimes more often.
Step to recreate:
Create new single player world all default settings.
Hit escape and click "Open to LAN"
Turn "Allow Cheats" to ON
Click "Start LAN World"
Explore the world for a few minutes
Hit Escape key and choose "Save and Quit to Title"
Repeat couple or so times until in hangs if neededTo me it acts like the network stream is not being closed every time.
NOTE: Upon force quitting the client the launcher does reappear with the Game Output tab selected but there are no errors.
JStack, WhatIsHang, and debug logs related to this issue
That bug appends only if the world is "open to LAN", since release 1.8.
That world was created in 1.8 too.
When I press Escape and click "Save and Quit to title", Minecraft freezes. I have to shut it down, then an error message pops saying "Java(SE) binary is not responding".
After that the launcher appear with bug informations on it.
It does not append every time, but around 1 out of 3 times.
Here is what is write in the launcher :
[17:42:54] [Server thread/INFO]: BartZeroSix lost connection: TextComponent{text='Disconnected', siblings=[], style=Style{hasParent=false, color=null, bold=null, italic=null, underlined=null, obfuscated=null, clickEvent=null, hoverEvent=null, insertion=null}} [17:42:54] [Server thread/INFO]: BartZeroSix left the game [17:42:54] [Server thread/INFO]: Stopping singleplayer server as player logged out [17:42:54] [Server thread/INFO]: Stopping server [17:42:54] [Server thread/INFO]: Saving players [17:42:54] [Server thread/INFO]: Saving worlds [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/Overworld [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/Nether [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/The End
From
MC-73057:Sometimes when opening a world to LAN the client will hang and require force quit when choosing "Save and Quit to Title".
This does not happen every time but rather once or twice out of 3-10 times trying it but sometimes more often.
Step to recreate:
Create new single player world all default settings.
Hit escape and click "Open to LAN"
Turn "Allow Cheats" to ON
Click "Start LAN World"
Explore the world for a few minutes
Hit Escape key and choose "Save and Quit to Title"
Repeat couple or so times until in hangs if neededTo me it acts like the network stream is not being closed every time.
NOTE: Upon force quitting the client the launcher does reappear with the Game Output tab selected but there are no errors.
is duplicated by
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Снимок экрана (143).png
is duplicated by
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
is duplicated by
is duplicated by
is duplicated by
JStack, WhatIsHang, and debug logs related to this issue
That bug appends only if the world is "open to LAN", since release 1.8.
That world was created in 1.8 too.
When I press Escape and click "Save and Quit to title", Minecraft freezes. I have to shut it down, then an error message pops saying "Java(SE) binary is not responding".
After that the launcher appear with bug informations on it.
It does not append every time, but around 1 out of 3 times.
Here is what is write in the launcher :
[17:42:54] [Server thread/INFO]: BartZeroSix lost connection: TextComponent{text='Disconnected', siblings=[], style=Style{hasParent=false, color=null, bold=null, italic=null, underlined=null, obfuscated=null, clickEvent=null, hoverEvent=null, insertion=null}} [17:42:54] [Server thread/INFO]: BartZeroSix left the game [17:42:54] [Server thread/INFO]: Stopping singleplayer server as player logged out [17:42:54] [Server thread/INFO]: Stopping server [17:42:54] [Server thread/INFO]: Saving players [17:42:54] [Server thread/INFO]: Saving worlds [17:42:54] [Server thread/INFO]: Saving chunks for level'Freebuild 1.8'/Overworld [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/Nether [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/The End
From
MC-73057:Sometimes when opening a world to LAN the client will hang and require force quit when choosing "Save and Quit to Title".
This does not happen every time but rather once or twice out of 3-10 times trying it but sometimes more often.
Step to recreate:
Create new single player world all default settings.
Hit escape and click "Open to LAN"
Turn "Allow Cheats" to ON
Click "Start LAN World"
Explore the world for a few minutes
Hit Escape key and choose "Save and Quit to Title"Repeat couple or so times until in hangs if neededTo me it acts like the network stream is not being closed every time.
NOTE: Upon force quitting the client the launcher does reappear with the Game Output tab selected but there are no errors.
The bug
When the host of a singleplayer world which was opened to LAN tries to close the world their game (client) may freeze.
The log shows that the server was successfully stopped though.[17:42:54] [Server thread/INFO]: BartZeroSix left the game [17:42:54] [Server thread/INFO]: Stopping singleplayer server as player logged out [17:42:54] [Server thread/INFO]: Stopping server [17:42:54] [Server thread/INFO]: Saving players [17:42:54] [Server thread/INFO]: Saving worlds [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/Overworld [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/Nether [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/The EndHow to reproduce
- Open a world
- Open it to LAN
- Try to close the world
Note: Since this bug seems to be caused by a race condition it could be possibly that you cannot reproduce this bug with some computers.
Code analysis and debugging results
JStack, WhatIsHang, and debug logs related to this issue
This bug seems to have the same cause like
MC-92255, which is caused by the method IntegratedServer.initiateShutdown being called twice.
The bug
When the host of a singleplayer world which was opened to LAN tries to close the world their game (client) may freeze.
The log shows that the server was successfully stopped though.[17:42:54] [Server thread/INFO]: BartZeroSix left the game [17:42:54] [Server thread/INFO]: Stopping singleplayer server as player logged out [17:42:54] [Server thread/INFO]: Stopping server [17:42:54] [Server thread/INFO]: Saving players [17:42:54] [Server thread/INFO]: Saving worlds [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/Overworld [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/Nether [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/The EndHow to reproduce
- Open a world
- Open it to LAN
- Try to close the world
Note: Since this bug seems to be caused by a race condition it could be possibl
ythat you cannot reproduce this bug with some computers.Code analysis and debugging results
JStack, WhatIsHang, and debug logs related to this issue
This bug seems to have the same cause like
MC-92255, which is caused by the method IntegratedServer.initiateShutdown being called twice.The bug
When the host of a singleplayer world which was opened to LAN tries to close the world their game (client) may freeze.
The log shows that the server was successfully stopped though.[17:42:54] [Server thread/INFO]: BartZeroSix left the game [17:42:54] [Server thread/INFO]: Stopping singleplayer server as player logged out [17:42:54] [Server thread/INFO]: Stopping server [17:42:54] [Server thread/INFO]: Saving players [17:42:54] [Server thread/INFO]: Saving worlds [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/Overworld [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/Nether [17:42:54] [Server thread/INFO]: Saving chunks for level 'Freebuild 1.8'/The EndHow to reproduce
- Open a world
- Open it to LAN
- Try to close the world
Note: Since this bug seems to be caused by a race condition it could be possible that you cannot reproduce this bug with some computers.
Code analysis and debugging results
JStack, WhatIsHang, and debug logs related to this issue
This bug seems to have the same cause like
MC-92255, which is caused by the method IntegratedServer.initiateShutdown being called twice.
is duplicated by
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
is duplicated by
is duplicated by
The bug still exists. I've been being disturbed by this from Minecraft 1.8 to 1.12.2.
is duplicated by
[Mojang] Cory Scheviak
![[Mojang] Panda](../../../data/avatars/users/41658.png){kind=small}
When ever I load a certain area of my world the attached crash happens.
If the world is started as a server only the client crashes, but the crash report should speak for itself.
Steps to reproduce:
1. Download the attached world file
2. Log into this world
3. Look down
Description: Tesselating block in world java.lang.IndexOutOfBoundsException at java.nio.Buffer.checkIndex(Buffer.java:538) at java.nio.DirectByteBuffer.putFloat(DirectByteBuffer.java:887) at bfd.b(SourceFile:414) at bge.a(SourceFile:225) at bgd.a(SourceFile:67) at bht.b(SourceFile:176) at bhp.a(SourceFile:78) at bho.b(SourceFile:121) at bfr.a(SourceFile:842)
Note that this crash might be environment dependent.
How the world got corrupted like this
I had the world open to LAN and when I left it Minecraft hung (MC-72943). After forcing the process to stop and restarting the crash happened when ever joining the world again.
Search disclaimer
The only unresolved issue I could find which might be related to this one is MC-81252, but it has a completely different stack trace. There is many other issues about the same/similar crashes but as they are resolved I just assume that they have different causes.
Potential Fix
The reason for the exception is that a buffer for rendering overflows.
package net.minecraft.client.renderer; ... public class WorldRenderer { ... private void growBuffer(int p_178983_1_) { LogManager.getLogger().warn("Needed to grow BufferBuilder buffer: Old size " + this.bufferSize * 4 + " bytes, new size " + (this.bufferSize * 4 + p_178983_1_) + " bytes."); this.bufferSize += p_178983_1_ / 4; ByteBuffer var2 = GLAllocation.createDirectByteBuffer(this.bufferSize * 4); this.rawIntBuffer.position(0); var2.asIntBuffer().put(this.rawIntBuffer); this.byteBuffer = var2; this.rawIntBuffer = this.byteBuffer.asIntBuffer(); this.rawFloatBuffer = this.byteBuffer.asFloatBuffer(); } public void setVertexState(WorldRenderer.State p_178993_1_) { this.rawIntBuffer.clear(); // This call causes the crash. Calling growBuffer() when needed fixes the crash for me. this.rawIntBuffer.put(p_178993_1_.func_179013_a()); this.rawBufferIndex = p_178993_1_.getRawBufferIndex(); this.vertexCount = p_178993_1_.getVertexCount(); this.vertexFormat = new VertexFormat(p_178993_1_.func_179016_d()); } ... }
Growing the buffer might be the right fix, but it could also be that the reason why it overflows is a bug in the first place.
So far this only seems to happen to me when flying in creative. Specifically when I press ESC while moving and press Save and Quit while the character is still gliding.
Edit: Which is also to say as long as I always make sure my feet are on the ground in my local LAN game it doesn't freeze on quit.
I can continuously reproduce that in a superflat world with Open To Lan. I think that it has to deal with new chunks being loaded and not yet generated. The reason why you need to be moving in creative is to start loading new chunks, it seems. (Obviously, in a more intensive custom world, gamemode 1 wouldn't be needed because you can just walk a chunk and the new area takes a while to load).
If I'm standing still (even if flying), there isn't any problem. Again, this is on a generic superflat world – Seed manually set to 0, and it's the default grass at layer 4 one. (Also, Game Mode 1)
I cannot reproduce this in an AMPLIFIED world, however. Odd, because I can find unloaded chunks.
I'll investigate further later.
@Kumasasa:
Customized worlds may take some minutes until being saved (chunks are still generated and saved at the same time)
Are you sure about this? 100% sure? Because if they weren't getting generated and saved at the same time, the game would hang forever like it is.
Also, what's the relationship between this ticket and MC-72943? Are they duplicates? Does Minecraft actually make it to the saving chunks screen in this one? (the other one explicitly states it doesn't, but this one I can't tell for sure).
@[Mod] Pokechu22 MC-72943 seems to be it. Thank you for linking it 
I think MC-72943 covers this issue. It has some randomness to it and also happened in 1.8.x to me.
Definitely something that should get fixed better sooner than later. Even a possible candidate for a 1.8.9 in my opinion.
![[Helper] gaspoweredpick](../../../data/avatars/users/80904.png){kind=small}
Duplicate of MC-72943 (maybe)
I can confirm this without LAN mode but i confirm this more of a lag problem that stays after you go to the menu. so maybe this is not MC-72943, if its not a duplicate, i can only confirm this caused by MC-11571 with the lag causing huge lag problems with the menu screen and taking a long time to save the game or not being able to save due to so much lag. taking a long time to save is probably intended or can be fixed to cause less lag.
Duplicate of MC-72943 (it's been specified that this only happens when open to lan is used).
Resolving as duplicate of MC-72943 since the original game output log of this ticket mentions a LAN game:
[CHAT] Local game hosted on port 56041
Duplicates MC-72943
The freeze is probably MC-72943 and does not happen for everyone.
Duplicate of MC-72943. Please go and upvote that ticket instead.
Duplicate of MC-72943. Please go and upvote that ticket instead.
Happening again as per MC-72943 (this issue is effectively a duplicate of that, but for a different means of reproduction). I haven't personally reproduced this variant, but I can confirm that the methods are again called twice in 18w20a, but not in 18w19b.
How long did you wait after 17:42:54 ?
I have waited more than 15 min the first time. After that only 5 minuts or so, but this time only 30 secondes just to have launcher's log.
It probably doesn't come from my PC (i mean not from RAM or something like that), because i have a pretty good PC (not a single problem even on huge modpack).
Is there a crash report generated in .minecraft/crash-reports?
It does not look like. The folder isn't even there. (I cleaned my .minecraft folder for the 1.8 release though.)
I can confirm this.
Here is a link
MC-73057to the bug report I submitted (marked duplicate .. sorry didn't think it was reported) anyways there is more info in my report that might help reproduce this bug.To me it appears maybe the network stream is not being closed every time.
P.S. I have personally left the client open for hours after it hangs and it never goes back to main menu.
Closely related to
MC-63802- same issue for dedicated serverI can confirm this on 1.8 through 1.8.1-pre2 on Ubuntu 14.04 LTS 32-bit. I get this a lot when I need to use a cheat command, like to switch to clear weather when rain lags my slow laptop. Same log output; looks like nothing happened.
Is this still an issue in 1.8.1-pre3 ? The related
MC-72806got fixed in that version.1.8.1-pre4 - Nope. Still there. Not resolved. :'(
This happens on 1.8.1 & 1.8.2-pre4
OS X 10.10.1 Java 8u25
The game gives no log info from the actual freeze.
Players need not join the game after opening to LAN for the freeze to occur.
I have waited over an hour before and we came back and it was still doing nothing. If the game is in fullscreen, I must force restart the computer.
Game music is still playing after clicking Save and Quit. Game log ends here:
No Launcher log entries after Save and Quit.
I forced the client to quit and got these log entries:
Game
Launcher
I have the same problem. Also on launcher log it said "game ended with bad state" and gives an error number but I can't remember the namer and find the launcher log... I googled that number, it's an "out of memory" error but I already allocated more memory and still have the same problem.
Cannot reproduce on 1.8.2-pre6
OS X 10.10.2 Java 8u31
Can't reproduce in 1.8.2-pre5, so I think that's the fix version.
EDIT: seems like everyone has this issue only sporadically. In any case, it has happened to me in 1.8.5. Java 8u45 OS X 10.10.3.
Oh wow this actually just happened to me!! I thought it was just lag from the internet <-- which it could very well be, for me at least. Yeah it just froze and usually the window says (not responding) but it didn't I had to close via task manager<--which said java said not repsonding. The log said nothing suspicious so I thought it was just normal but I have noticed that ANYTIME minecraft is closed that their is a slight 'freezing' (you get the loading screen but without the words) and then it goes to the title screen. Sometimes it says not responding but it usually fixes itself within a minute.
EDIT: and I am currently using 1.8.2pre6
Same issue. Vanilla 1.8.3 on Ubuntu 12.04 64-bit. Has occurred 1/1 time played on one world created in 1.8.3 and 1/2 times played on another world created in 1.8.3. So it has occurred 2 times of the 3 total times I have played a LAN world. First time it happened I left overnight and it did not self-correct.
I have same issue too, but it may corrupt the save
I note that if you have had a LAN user join your game, then when you quit, it doesn't hang.
Same issue on Vanilla Minecraft 1.8.3 on Windows 7 SP1 64-bit. Happens every time I try to exit a LAN world in 1.8.3. Java version 1.8.0_40.
Same issue on Vanilla 1.8.4, Mac OS. Happens every time I exit a LAN world. Java version 1.8.0_45. This doesn't correct itself overnight.
Think this'll corrupt any data? ARE MY FARM ANIMALS OKAY?!?
Confirmed for
confirmed for 1.8.5
Java 8u45
OS X 10.10.3
I also just commented on numerous other reports that are identical to this. This ticket is not the oldest one, but I guess it's the only currently open one and it has a decent amount of attention.
Linking them all up would really help though. Especially for older users who now have fellow players in the same boat as them. It's good to know you shouldn't have been brushed off.
This just happened to me on 1.8.7 with a brand new download of the launcher, v1.6.11. I had been playing with it opened to LAN and one other person (who had logged off before I exited). I had to kill the window forcefully.
latest.log file attached. This has been happening to me ever since I can remember on 1.8+
OS: Windows 7 x64 SP1 Professional
Proc: Intel Core i7 940
Motherboard: EVGA x58 SLI
VGA: MSI AMD 6950
RAM: 12GB
Java: 8 Update 31 (64-bit)
Has this seriously not been fixed yet? Opened October of 2014 and still no resolution?
Confirmed this bug still exists in 1.8.7 because it happens to me almost 100% of the time I play on LAN. Force close is the only way to close Minecraft. Leaving it open for hours doesn't matter.
Froze on my first test on 15w31a. Still no unique or interesting log entries. World still saves fine before the freeze. The freeze still occurs on the pause screen while the "Save and Quit to Title" button is depressed.
Wellllllllllll, this doesn't always happen, usually only when left open for an extended period of time, (including when I'm not AFK), and only like 30-45% of the time. :\
It just happened to me on stream in 15w40b. So I can confirm for 15w40b.
Check my log on
MC-71357, it will show you what happens.I have the same problem as well.
Are they duplicates?
Confirmed on MC 1.8.8, still unresolved?
Confirmed. Also to note, the game freezes only for the host.
This is my second freeze
Check the log with this name:
mc_freeze_03_10_2015.txt
Confirmed for 15w41b.
Confirmed for 15w46a
Confirm for 15w47a
Confirm for 15w50a.
This problem is happening for me too now my kids have two accounts and have been running Open to LAN games.
Host Computer: OS X 10.11.1, Minecraft 1.8, Launcher 1.6.44
This is the one usually running as the host when it hangs.
I am running Ubuntu 14.04 LTS and notice that if I have top running in a shell and use the "Open to LAN" feature of Minecraft in single player world, running in OpenJDK/JRE 7, launcher version 1.6.44, MC Version 1.8.9, then the game will exit normally and not freeze up. I usually set other players mode as spectator, but there are no other players on my LAN, and set the cheats on because I use the gamemode command to change mode. I have tried this twice, and it has worked fine both times. I do not know the intricacies of top, but understand that it is like the task manager in MS Windows. I hope this helps to resolve the isssue.
Very likely the same reason as for
MC-92255.The client is calling initiateShutdown() for the server twice.
Confirmed for 16w02a
Confirmed for 16w03a.
After my fullscreen Minecraft session froze in Win10, I am unable to alt-tab away from Minecraft or recover my system. CTRL-Alt-Delete doesn't pull up the task manager, and Alt-F4 has no effect. Does anyone have any other tips for killing the Minecraft session short of a hard reboot?
Edit: Nevermind. If you wait long enough (20 mins??), ctrl-alt-delete will kick in.
Confirmed for 16w04a. Made sure not to be in fullscreen this time. Windows is much better at ending the frozen program if you can click the X on the window chrome. Hope this bug gets fixed!
Confirmed for 16w05a.
Confirmed for 16w05b.
Confirm for 1.9-pre1
Confirm for 1.9-pre2
Confirm for 1.9-pre3
Confirm for 1.9-pre4
Confirm for 1.9
I also have this problem. Minecraft 1.9 (on Win10x64.) Final messages: Stopping singleplayer server; Stopping server; Saving players; Saving worlds; Saving chunks .../Overworld; then /Nether; then /The End. No players had left the Overworld.
I got around this problem by enabling cheats at world generation time. Since I am playing only singleplayer, I do not need to open to LAN and just wanted to be able to enter command to change game mode and difficulty. I do not like to cheat but view cheats as just a way for a singleplayer to access some additional functionality. CAVEAT: Anything with great potential has an equal likelihood of great exploitation by others.
From the start of 1.8 to 1.9. Wow. This bug has sure been overlooked.
EDIT: Just happened to me. Kinda annoying.
@TheRSC it certainly seems like it's been overlooked. I reported it back in 1.8 and at each update when it still happened came back to re-report, but other people kept beating me to it. Been following it the whole time and the only updates I ever see are more reports of it. No one ever comments on fixing it...
@Bryan I don't think its that. They still have no idea what it causing this bug. Like for example, mine has been working great since the 1.9 snapshots and I think since 1.8.8 I have personally dealt with this bug myself and I can tell you that it is very strange considering it still effects you among others. Since it does not effect me anymore and probably others as well, Just keep trying to duplicate it and if you think it will definitely do it again, just before you press save and quit hold f3 + C for a few seconds to force a crash report then attach it this ticket. If anything, this might help Mojang fix this, if they can find anything strange in the reports. It's a shot.
ALSO: Make sure the internet connection isn't going in and out while you have it open to lan. Mine froze when the internet went down and I tried to save and quit.
Confirm for 16w14a
Confirm for 16w15a
Confirm for 1.9.2
That's already marked as affected.
Happens to me as well on 1.9.2.
Was already marked as affected. (for the second time)
Confirm for 1.9.4
Confirm 16w20a.
Confirmed in 1.10.2.
I am tweeting some people at Mojang about this. Hopefully then it will get some attention.
Because they said:
1.10.2 release notes:
This is a smaller update taking care of some of the most annoying reported bugs. We are also planning to release another update for 1.10.x in a few weeks that takes care of some less critical but still annoying issues.
This better be one of them.
Not sure if this bug might be "one of them", but I don't think it'd help to tweet it randomly or specifically.
This bugpost got a decent amount of votes and has been noticed.
But some other bugs might have still priority, I could name at least 2 dozens of them from my perspective rightaway.
This is not a really "critical", but admittedly "annoying" bug.
If you want to get this bug being fixed maybe faster (if possible) try to collect some votes from the community by opening a Redditpost or tweet it or make a YT video about it etc. }=)
That being said, it's not a guarantee of course, sometimes some bugs are not easy to fix, despite them looking easy at first glance, so who knows.
I really just want to make sure they know about it. Though, yes, some more votes will help. I might make a Reddit post.
Reproduced in 1.10.2 successfully. I grabbed some info using WhatIsHang and also with jstack:
And I also had debug logging enabled:
Hopefully some of this information is useful. I'm not completely sure how to interpret it, but it looks like the integrated server is hanging on the call to Futures.getUnchecked in IntegratedServer.initiateShutdown.
Still freeze up after lan exit on all my computers. Mac Os x, Ubuntu and Windows 3 different machines 3 different OS Versions all same results. Running 1.10.2 Minecraft
[Mod] Pokechu22, I assumed as well that the initiateShutdown method is the cause. Please link from the description to your comment.
please fix this it's been 30 minutes for me
This might be fixed in our upcoming snapshot, due to another fix. It would be great if you can test it when the snapshot is released and see if you can get a repeat. Thanks much!
Please see if it still occures in the next snapshot.
Still present and still hanging on Futures.getUnchecked. I've attached a report generated by jstack -l <pid>: MC-72943_jstack_16w43a.txt
.
Confirm for 1.11
Using version 1.11.2 the 'Save and Quit to Title' always states 'Not Responding' after a Open to LAN game. The machine that joins the LAN game is able to gracefull quit first but when the machine that opened to LAN quits we always get Not responding / greyed out window.
When forcing close with the big X JAVA error is reported
Description: A problem caused this program to stop interacting with Windows.
Problem signature:
Problem Event Name: AppHangB1
Application Name: javaw.exe
Application Version: 8.0.25.18
Application Timestamp: 54345ca0
Hang Signature: faa2
Hang Type: 0
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057
Additional Hang Signature 1: faa2972dfdc2cfbd3f39770e45243ed0
Additional Hang Signature 2: 1db5
Additional Hang Signature 3: 1db56fbfdd30d2bb0ea1ba4130d6ee8c
Additional Hang Signature 4: faa2
Additional Hang Signature 5: faa2972dfdc2cfbd3f39770e45243ed0
Additional Hang Signature 6: 1db5
Additional Hang Signature 7: 1db56fbfdd30d2bb0ea1ba4130d6ee8c
Hope this helps solve what seems like an excessively long remediation for a very frustrating problem.
This has been happening since the 1.9 snapshot at least. It even happens on occasion in the full releases of the updates, not just snapshots.
I can confirm this happens to me
I have one mod installed and that is Optifine, could it be a problem with that?
Happens on vanilla 1.11.2, also. Java 1.8.0_131, macos 10.12.4.
This happens to me as well. No mods. Version information below:
Confirmed for 1.12.1, behavior as described in title.
EDIT: Just saw it was already described as affected. Nevermind.
Can confirm for 17w47b.
Confirm for 17w50a
Confirming this issue for 1.12.2 with forge running many mods. I believe this issue happens much more often with mods, though I am unaware whether it is a specific mod or forge itself.
As I understand it, it's a race condition, and having a bunch of mods will usually lead to slowdown, which can exacerbate the issue.
Has anyone experienced this in recent snapshots? I think it might be fixed, in that I haven't been able to reproduce it, but I've also changed my setup a bit and it may be that it just doesn't happen as often on my machine.
I just had this happen to my girlfriend. I'm not sure how to find out which snapshot that we are running. But we just installed the game a few days ago, so it should be on the newest version (1.12.2 I believe)
Snapshots are the development builds, which need to manually be enabled in the launcher (and aren't completely stable); they have names like 18w11a (year 2018 week 11, build a). If you haven't changed anything, then you're on release 1.12.2. You can check just by looking at the window title (or pressing F3 in-game).
Appears to have been fixed in 18w01a. IntegratedServer.initiateShutdown is only called once (from the client thread) in 18w01a, while it was called on both the server and client threads in prior versions. Checked with JDB, by setting an appropriate breakpoint; in 1.12.2 it is chd.x; in 17w50a it is (per forge's MCPInfo) clm.q; and in 18w01a it is cmd.q. Unfortunately I'm not entirely sure why it's not getting called twice anymore, as I don't see what changed.
This just happened to me on 1.13 Pre-Release 1.
Hm, my earlier testing made it seem like it was fixed in 18w01a. Will double-check and see if the same debug stuff I did earlier still shows it as fixed or not.
Can definitely confirm that the issue has returned. It was not present in 18w19b (dhm.q), but is definitely present in 18w20a (dhq.q) (and 18w20c (dhr.q)).
Why the status of the issue is resolved? It remains in almost every update. Cannot say it is critical though. While the game I play with my wife, crashes almost every time, it does not corrupt save data as it seems. But it became VERY annoying when we started playing with big modpacks like Sevtech, as changing the world is a pain, because loading the game again takes 5 minutes on my high end PC, and 15 minutes on my wife's laptop.
It's been fixed in 1.13. If you're using modpacks, you're almost certainly running an older (and now unsupported, though mods haven't been released for newer versions yet) version, where this has not yet been fixed.
Happened to me on a ModPack , Version 1.10.2 , LAN with my brother , Waited 20 minutes , Still Happening , Can't access my old world though , Anyone found a solution ?
We do not support modded versions of the game, nor do we support modified launchers, nor do we support outdated versions of the game.
This bug is fixed by updating to a current version of the game; at least 1.13.