Adam Dalgleish
Assigned
Reported
Comments
Is this still being worked on?
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.
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...
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.
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.
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.
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.
@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. 😉
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.
Attached the batch file that causes my issues when trying to log the error.
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?)
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
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.
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".
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?
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.