Adam Dalgleish
- xelphene
- xelphene
- Europe/London
- Yes
- No
MC-2824
When this bug happens:
I start Minecraft then go onto "Multiplayer".
I click on any server (does not matter whether it has been detected as accessible or not accessible) and click join.
On the loading screen (searching for server... / joining server...) or after Minecraft fails to join a server I click cancel.
I am now back on the menu screen as normal and I click the "Multiplayer" button again.
Minecraft instantly freezes and becomes totally unresponsive. Basically it crashes. However it does not close on its own or even say "not responding" - it just sits there frozen.
When I go to close it with Task Manager, Windows tells me that "Java Platform (SE) Binary has stopped working".Extra Info:
I know of other people on the forums having this bug as early as 1.3.1 and having it all the way up to the present (as have I).On top of this problem, for myself and several others this bug always causes the "When Minecraft Closes, Javaw.exe stays running" bug. I do not know if the two bugs have some sort of link but because the javaw bug already has a ticket (searching "javaw.exe not closing" should find it) I will not go into detail.
When this bug happens:
I start Minecraft then go onto "Multiplayer".
I click on any server (does not matter whether it has been detected as accessible or not accessible) and click join.
On the loading screen (searching for server... / joining server...) or after Minecraft fails to join a server I click cancel.
I am now back on the menu screen as normal and I click the "Multiplayer" button again.
Minecraft instantly freezes and becomes totally unresponsive. Basically it crashes. However it does not close on its own or even say "not responding" - it just sits there frozen.
When I go to close it with Task Manager, Windows tells me that "Java Platform (SE) Binary has stopped working".Extra Info:
I know of other people on the forums having this bug as early as 1.3.1 and having it all the way up to the present (as have I).On top of this problem, for myself and several others this bug always causes the "When Minecraft Closes, Javaw.exe stays running" bug. I do not know if the two bugs have some sort of link but because the javaw bug already has a ticket (searching "javaw.exe not closing" should find it) I will not go into detail.
Post Script - What happens when trying to get crash report:
I tried all three methods to get a crash report stated on the Minecraft Wiki.
When I start the batch file, Minecraft starts normally as it should do. I replicate the crash (Multiplayer -> any server -> cancel -> multiplayer) but the log file does not say anything past "connecting to server whateveritwas". I close Minecraft with Task Manager, which suddenly tells me that I am using 98% of my memory and the culprit is the process "java.exe" that has just started leaking memory massively and like the javaw.exe bug metioned above, nothing can close it. To top the problem off, I still have no more data in my crash report because the batch file trying to record my internal commands has been overloaded by whatever is crashing Minecraft and CMD and the whole of System 32 have been taken down by it! (Last step, force shutdown using tower button angryface)
When this bug happens:
I start Minecraft then go onto "Multiplayer".
I click on any server (does not matter whether it has been detected as accessible or not accessible) and click join.
On the loading screen (searching for server... / joining server...) or after Minecraft fails to join a server I click cancel.
I am now back on the menu screen as normal and I click the "Multiplayer" button again.
Minecraft instantly freezes and becomes totally unresponsive. Basically it crashes. However it does not close on its own or even say "not responding" - it just sits there frozen.
When I go to close it with Task Manager, Windows tells me that "Java Platform (SE) Binary has stopped working".Extra Info:
I know of other people on the forums having this bug as early as 1.3.1 and having it all the way up to the present (as have I).On top of this problem, for myself and several others this bug always causes the "When Minecraft Closes, Javaw.exe stays running" bug. I do not know if the two bugs have some sort of link but because the javaw bug already has a ticket (searching "javaw.exe not closing" should find it) I will not go into detail.
Post Script - What happens when trying to get crash report:
I tried all three methods to get a crash report stated on the Minecraft Wiki.
When I start the batch file, Minecraft starts normally as it should do. I replicate the crash (Multiplayer -> any server -> cancel -> multiplayer) but the log file does not say anything past "connecting to server whateveritwas". I close Minecraft with Task Manager, which suddenly tells me that I am using 98% of my memory and the culprit is the process "java.exe" that has just started leaking memory massively and like the javaw.exe bug metioned above, nothing can close it. To top the problem off, I still have no more data in my crash report because the batch file trying to record my internal commands has been overloaded by whatever is crashing Minecraft and CMD and the whole of System 32 have been taken down by it! (Last step, force shutdown using tower button angryface)When this bug happens:
I start Minecraft then go onto "Multiplayer".
I click on any server (does not matter whether it has been detected as accessible or not accessible) and click join.
On the loading screen (searching for server... / joining server...) or after Minecraft fails to join a server I click cancel.
I am now back on the menu screen as normal and I click the "Multiplayer" button again.
Minecraft instantly freezes and becomes totally unresponsive. Basically it crashes. However it does not close on its own or even say "not responding" - it just sits there frozen.
When I go to close it with Task Manager, Windows tells me that "Java Platform (SE) Binary has stopped working".Extra Info:
I know of other people on the forums having this bug as early as 1.3.1 and having it all the way up to the present (as have I).On top of this problem, for myself and several others this bug always causes the "When Minecraft Closes, Javaw.exe stays running" bug. I do not know if the two bugs have some sort of link but because the javaw bug already has a ticket (searching "javaw.exe not closing" should find it) I will not go into detail.
Post Script - What happens when trying to get crash report:
I tried all three methods to get a crash report stated on the Minecraft Wiki.
When I start the batch file, Minecraft starts normally as it should do. I replicate the crash (Multiplayer -> any server -> cancel -> multiplayer) but the log file does not say anything past "connecting to server whateveritwas". I close Minecraft with Task Manager, which suddenly tells me that I am using 98% of my memory and the culprit is the process "java.exe" that has just started leaking memory massively and like the javaw.exe bug metioned above, nothing can close it. To top the problem off, I still have no more data in my crash report because the batch file trying to record my internal commands has been overloaded by whatever is crashing Minecraft and CMD and the whole of System 32 have been taken down by it! (Last step, force shutdown using tower button and sigh heavily...)
When this bug happens:
I start Minecraft then go onto "Multiplayer".
I click on any server (does not matter whether it has been detected as accessible or not accessible) and click join.
On the loading screen (searching for server... / joining server...) or after Minecraft fails to join a server I click cancel.
I am now back on the menu screen as normal and I click the "Multiplayer" button again.
Minecraft instantly freezes and becomes totally unresponsive. Basically it crashes. However it does not close on its own or even say "not responding" - it just sits there frozen.
When I go to close it with Task Manager, Windows tells me that "Java Platform (SE) Binary has stopped working".Extra Info:
I know of other people on the forums having this bug as early as 1.3.1 and having it all the way up to the present (as have I).On top of this problem, for myself and several others this bug always causes the "When Minecraft Closes, Javaw.exe stays running" bug. I do not know if the two bugs have some sort of link but because the javaw bug already has a ticket (searching "javaw.exe not closing" should find it) I will not go into detail.
Post Script - What happens when trying to get crash report:
I tried all three methods to get a crash report stated on the Minecraft Wiki.
When I start the batch file, Minecraft starts normally as it should do. I replicate the crash (Multiplayer -> any server -> cancel -> multiplayer) but the log file does not say anything past "connecting to server whateveritwas". I close Minecraft with Task Manager, which suddenly tells me that I am using 98% of my memory and the culprit is the process "java.exe" that has just started leaking memory massively and like the javaw.exe bug metioned above, nothing can close it. To top the problem off, I still have no more data in my crash report because the batch file trying to record my internal commands has been overloaded by whatever is crashing Minecraft and CMD and the whole of System 32 have been taken down by it! (Last step, force shutdown using tower button and sigh heavily...)When this bug happens:
I start Minecraft then go onto "Multiplayer".
I click on any server (does not matter whether it has been detected as accessible or not accessible) and click join.
On the loading screen (searching for server... / joining server...) or after Minecraft fails to join a server I click cancel.
I am now back on the menu screen as normal and I click the "Multiplayer" button again.
Minecraft instantly freezes and becomes totally unresponsive. Basically it crashes. However it does not close on its own or even say "not responding" - it just sits there frozen.
When I go to close it with Task Manager, Windows tells me that "Java Platform (SE) Binary has stopped working".Extra Info:
I know of other people on the forums having this bug as early as 1.3.1 and having it all the way up to the present (as have I).On top of this problem, for myself and several others this bug always causes the "When Minecraft Closes, Javaw.exe stays running" bug. I do not know if the two bugs have some sort of link but because the javaw bug already has a ticket (https://mojang.atlassian.net/browse/MC-1408#comment-20993) I will not go into detail.
Post Script - What happens when trying to get crash report:
I tried all three methods to get a crash report stated on the Minecraft Wiki.
When I start the batch file, Minecraft starts normally as it should do. I replicate the crash (Multiplayer -> any server -> cancel -> multiplayer) but the log file does not say anything past "connecting to server whateveritwas". I close Minecraft with Task Manager, which suddenly tells me that I am using 98% of my memory and the culprit is the process "java.exe" that has just started leaking memory massively and like the javaw.exe bug metioned above, nothing can close it. To top the problem off, I still have no more data in my crash report because the batch file trying to record my internal commands has been overloaded by whatever is crashing Minecraft and CMD and the whole of System 32 have been taken down by it! (Last step, force shutdown using tower button and sigh heavily...)
minecraft-report.bat
Windows Vista, Java Version 7 update 7 32-bit (other users have it in Java 64-bit)
Whenever a zombie or skeleton drops chain boots that they spawned with, they are named "Chainmail Boots". This is written in regular text (or blue if enchanted), to show that the name is the item's default name. However the rest of the chain armour set is named using the convention "Chain <item>" and I'm pretty sure boots should be too.
Furthermore, when you repair the boots with iron ingots / combine with another chain boots / add an enchanted book in the anvil, the name "Chainmail Boots" is automatically put into italics in the way that custom names (and only custom names) are. Alternatively put a non-italics "Chainmail Boots" into the anvil and edit its name to "Chain Boots". The anvil does not give the option to take the item from the right-hand slot with the new name, it just has the red cross through the arrow as if you had not altered the name at all.
These two things suggest the "Chainmail Boots" is correctly named "Chain Boots" in the part of the item data that the anvil checks and only the name that is displayed in the GUI is typoed. (This would explain why anvils think it is named "Chain Boots", and when you repair / combine it the name goes italic because the anvil thinks the name "Chainmail Boots" in the name slot was put there by the player and therefore gives it that custom name, complete with italic font.)Steps to reproduce:
I noticed this with a couple of skeletons / zombies naturally spawned in my mob XP farm (hard mode) when I was lucky enough to get them to drop some of their chain armour, but I expect it would work if you used spawn eggs until you got a mob wearing chain boots and (with luck) killed it and got the item.Hopefully I haven't missed anything. Should be a pretty easy one to fix seeing as it just looks like a typo. (Not sure how its name-for-the-anvil and name-for-the-player are different though...)
This example is specific to when you are using the Canadian English language:
Whenever a zombie or skeleton drops chain boots that they spawned with, they are named "Chainmail Boots". This is written in regular text (or blue if enchanted), to show that the name is the item's default name. However the rest of the chain armour set is named using the convention "Chain <item>" and I'm pretty sure boots should be too.
Furthermore, when you repair the boots with iron ingots / combine with another chain boots / add an enchanted book in the anvil, the name "Chainmail Boots" is automatically put into italics in the way that custom names (and only custom names) are. Alternatively put a non-italics "Chainmail Boots" into the anvil and edit its name to "Chain Boots". The anvil does not give the option to take the item from the right-hand slot with the new name, it just has the red cross through the arrow as if you had not altered the name at all.
These two things suggest the "Chainmail Boots" is correctly named "Chain Boots" in the part of the item data that the anvil checks and only the name that is displayed in the GUI is typoed. (This would explain why anvils think it is named "Chain Boots", and when you repair / combine it the name goes italic because the anvil thinks the name "Chainmail Boots" in the name slot was put there by the player and therefore gives it that custom name, complete with italic font.)Steps to reproduce:
I noticed this with a couple of skeletons / zombies naturally spawned in my mob XP farm (hard mode) when I was lucky enough to get them to drop some of their chain armour, but I expect it would work if you used spawn eggs until you got a mob wearing chain boots and (with luck) killed it and got the item.
Chain Boots called "Chainmail Boots" when dropped by mobsAnvils don't recognise language pack variations
Strange behaviour in an anvil. Only seems to be Canadian English.
This example is specific to when you are using the Canadian English language:
Whenever a zombie or skeleton drops chain boots that they spawned with, they are named "Chainmail Boots". This is written in regular text (or blue if enchanted), to show that the name is the item's default name. However the rest of the chain armour set is named using the convention "Chain <item>" and I'm pretty sure boots should be too.
Furthermore, when you repair the boots with iron ingots / combine with another chain boots / add an enchanted book in the anvil, the name "Chainmail Boots" is automatically put into italics in the way that custom names (and only custom names) are. Alternatively put a non-italics "Chainmail Boots" into the anvil and edit its name to "Chain Boots". The anvil does not give the option to take the item from the right-hand slot with the new name, it just has the red cross through the arrow as if you had not altered the name at all.
These two things suggest the "Chainmail Boots" is correctly named "Chain Boots" in the part of the item data that the anvil checks and only the name that is displayed in the GUI is typoed. (This would explain why anvils think it is named "Chain Boots", and when you repair / combine it the name goes italic because the anvil thinks the name "Chainmail Boots" in the name slot was put there by the player and therefore gives it that custom name, complete with italic font.)Steps to reproduce:
I noticed this with a couple of skeletons / zombies naturally spawned in my mob XP farm (hard mode) when I was lucky enough to get them to drop some of their chain armour, but I expect it would work if you used spawn eggs until you got a mob wearing chain boots and (with luck) killed it and got the item.Edit:
Also happens with "Chain Trousers" and "Iron Spade" in English (UK). I expect it will happen with any item that is called something different to US English in the currently selected language.
This example is specific to when you are using the Canadian English language:
Whenever a zombie or skeleton drops chain boots that they spawned with, they are named "Chainmail Boots". This is written in regular text (or blue if enchanted), to show that the name is the item's default name. However the rest of the chain armour set is named using the convention "Chain <item>" and I'm pretty sure boots should be too.
Furthermore, when you repair the boots with iron ingots / combine with another chain boots / add an enchanted book in the anvil, the name "Chainmail Boots" is automatically put into italics in the way that custom names (and only custom names) are. Alternatively put a non-italics "Chainmail Boots" into the anvil and edit its name to "Chain Boots". The anvil does not give the option to take the item from the right-hand slot with the new name, it just has the red cross through the arrow as if you had not altered the name at all.
These two things suggest the "Chainmail Boots" is correctly named "Chain Boots" in the part of the item data that the anvil checks and only the name that is displayed in the GUI is typoed. (This would explain why anvils think it is named "Chain Boots", and when you repair / combine it the name goes italic because the anvil thinks the name "Chainmail Boots" in the name slot was put there by the player and therefore gives it that custom name, complete with italic font.)Steps to reproduce:
I noticed this with a couple of skeletons / zombies naturally spawned in my mob XP farm (hard mode) when I was lucky enough to get them to drop some of their chain armour, but I expect it would work if you used spawn eggs until you got a mob wearing chain boots and (with luck) killed it and got the item.Edit:
Also happens with "Chain Trousers" and "Iron Spade" in English (UK). I expectit will happen with any item that is called something different to US English in the currently selected language.This example is specific to when you are using the Canadian English language:
Whenever a zombie or skeleton drops chain boots that they spawned with, they are named "Chainmail Boots". This is written in regular text (or blue if enchanted), to show that the name is the item's default name. However the rest of the chain armour set is named using the convention "Chain <item>" and I'm pretty sure boots should be too.
Furthermore, when you repair the boots with iron ingots / combine with another chain boots / add an enchanted book in the anvil, the name "Chainmail Boots" is automatically put into italics in the way that custom names (and only custom names) are. Alternatively put a non-italics "Chainmail Boots" into the anvil and edit its name to "Chain Boots". The anvil does not give the option to take the item from the right-hand slot with the new name, it just has the red cross through the arrow as if you had not altered the name at all.
These two things suggest the "Chainmail Boots" is correctly named "Chain Boots" in the part of the item data that the anvil checks and only the name that is displayed in the GUI is typoed. (This would explain why anvils think it is named "Chain Boots", and when you repair / combine it the name goes italic because the anvil thinks the name "Chainmail Boots" in the name slot was put there by the player and therefore gives it that custom name, complete with italic font.)Steps to reproduce:
I noticed this with a couple of skeletons / zombies naturally spawned in my mob XP farm (hard mode) when I was lucky enough to get them to drop some of their chain armour, but I expect it would work if you used spawn eggs until you got a mob wearing chain boots and (with luck) killed it and got the item.Edit:
Also happens with "Chain Trousers" and "Iron Spade" in English (UK). They do not have to be mob drops - they can also be crafted or spawned with creative. I expect this bug will happen with any item that is called something different to US English in the currently selected language.
I get this bug too. Javaws stay open and can't be closed after the game crashes when I cancel joining a server and click multiplayer again. Perhaps the bugs are linked.
Something interesting I found out: when the javaw is open, you are not allowed to edit bin->minecraft because it is "open in another program". So maybe it is not just javaw glitching - when the game crashes, parts of it stay running in an unclosable way?
Also is there a way that the poster can update this report to say it is still happening in 1.4.4pre? Because it is. And I'd hate to think that it will be ignored because 1.4.2 reports are now "obsolete".
Sorry, forgot to get a crash report because the javaw bug mentioned makes it hard to continue using my computer after MC has crashed without a restart. I will attach a crash report tomorrow if that is okay because it's getting a bit late now.
OK, as said above, I cannot get a crash report because the crash crashes the crash report recorder. With the weird stuff with Java staying open, I am inclined to think that this bug (or parts of it) is somehow linked to the "Javaw.exe not closing bug" HERE: https://mojang.atlassian.net/browse/MC-1408
Could all those with this bug please see if this bug also happens: https://mojang.atlassian.net/browse/MC-2824#comment-20990 For me it seems like they are linked, it would just be really helpful to know if they are part of the same issue or not. (Even you don't get the clicking multiplayer crash, do you get the indestructible java.exe if you try using a batch file to make a log of Minecraft closing incorrectly? And does it crash System 32 for you too?)
Attached the batch file that causes my issues when trying to log the error.
The log file says Minecraft starts, I log in, I try to join server then nothing else because the MC crash crashes system 32 without giving it a chance to record the crash in the log.
Edit: The main reason I attached the batch is so that people can check that I didn't make any errors in it that could have compounded the bugs I was trying to record. Although as it was copy-pasted from the wiki, that seems unlikely.
@Daniel That sounds maybe like a more complex route to the same problem. Does the crash also happen for you just when clicking cancel on "connect to server..." then "multiplayer" without having being on a server beforehand?
Whatever this bug is, it seems quite a tricky one to pin seeing as it looks like we can't take crash logs... Maybe if I take my entire PC to Minecon Dinnerbone or somebody can have a look at it.
Can confirm this exact issue.
I ask that sometimes mods need to be more open-minded about these sort of Java-crashing bugs. In my case I can't take a bug report without it crashing my System 32 for some reason (that itself is a reason this bug should be taken seriously - how much rubbish is it throwing through the console that it crashes the OS itself on older computers?!), so perhaps not everything has an obvious answer in the crash log.
Well there you go Mojang - if you need to know what's wrong so you can fix it just go and look at what that mod alters.
Oh wow, turns out my language had set itself to Canadian English (WHY!?) and the bug fixes itself when you switch back to UK / US English.
Found items doing this in English (UK) language. They do the same glitchy behaviours with anvils. I expect it will be the same with any item that is called something different to the US name in any language; because it is beginning to look like the root cause is anvils check if an item is still its original name using the English (US) name list not the currently selected language.
Oops, forgot to mention it was multiplayer (sorry). It doesn't happen for me in single player. Do servers have a set language that could be overriding anvils detecting your own language?
Edit: Looking at other anvil bug reports, there are a few also to do with US English being the only language that works fully as intended...
Not sure if it is the same issue, but when I breed a 26 heart horse the first time it jumps the health drops to 11 hearts.
Is this still being worked on?
Well, it is K9 causing the problem so Mojang shouldn't be the ones altering their perfectly good code to get around it. I just uninstalled K9 seeing as it is the thing that is broken and is unlikely to be fixed soon.