Apocalypsing

I already know that pressing ESC is supposed to return to the main menu (or exit the pause menu ingame). The actual problem I'm trying to get across is that game settings aren't being saved properly. I'm highly confident that this is a bug, since this only affects changing resource packs. If I, for example, change the graphical and multiplayer chat settings and then press ESC, the changes are saved (I only just discovered this out of accident). If I follow the same process with resource packs, the changes aren't saved like they used to. See the inconsistency?

Affects 1.6 as well, right up to 1.6.2.

I was about to report the same issue. Although the crash is fixed now, on my end it was caused by 13w26a no longer recognising custom languages, regardless of their location in /assets/lang or a resource pack. This issue still exists in 1.6pre. This is kinda off-topic though.

Confirmed as still an issue in the 1.6 pre-release.

Seems to be fixed in 13w26a, I can't reproduce it any more as well. Thanks for fixing this so quickly Grum.

Still exists in 13w25c. 1.6 is due for next week and I'm becoming increasingly concerned that this annoying bug won't be fixed by then. I'm surprised it's taking so long to acknowledge and fix. I know from a development perspective that Minecraft is complex software and inevitably suffers from a lot of bugs, but this issue sounds like a simple rendering/draw order mix-up like a few other people have said.

I'm surprised there hasn't been much activity for this bug report recently. I'm coming here to confirm that this annoying bug still exists in stable release 1.5.2. It's a semi-rare, randomly-occurring bug, and I've noticed it in some form or another ever since buttons were initially implemented (sometime in Alpha/Beta).

I think the only way of fixing this right now is to place a repeater facing away from the adjacent block where the button is placed, to help sustain the pulse. Although this method won't be practical for things like small button-operated iron doors, for example.

1.5.2 seems to have fixed the issue for me with 64x64 packs, but 128x128 packs and higher still have issues. However I can confirm that the problem has been fixed completely for all texture resolutions in the 13w18 snapshot though, which is good news.

The problem still persists in 1.5.2. In 1.5.1 and 1.5 I was getting said performance issues with 64x64 textues and higher. In 1.5.2, performance issues aren't noticable with the same 64x64 texture pack (Defscape), but higher-resolution texture packs (128x128+) still have performance issues. There is also a pretty severe memory leak which occurs when switching/loading texture packs.

However, not all hope is lost. In the 13w18 snapshots, the performance issues have disappeared, and so has the memory leak. I did some testing using 128x128, 256x256, and 512x packs. I was able to run the 512x512 texture pack with only 1GB of RAM allocated to Minecraft, which is amazing to see. So the issue appears to be fixed for the future 1.6 release. One of the things listed in that snapshot's changelog was a "new texture loading system", and I'm guessing that Mojang rewrote the texture rendering portion of Minecraft's game engine, to better adapt to the new texture formatting added in 1.5.

If anyone is curious, I was testing on a Core i5 3570K and a HD 7870. Frame rate was always above 100 FPS with all settings maxed out, even with the 512x512 pack I tested, which was just over 200MB in size.

I had some really odd trouble getting a 256x pack to load, when testing the 1.5.2 release. When I clicked on the 256x pack to select it, Minecraft would freeze, as usual, but then after some time, the default texture pack would come up selected instead. I repeatedly clicked the 256x pack again and again until Minecraft crashed due due a lack of memory allocated. I had 2GB out of my system's 8GB allocated just FYI. I also got an OS warning, where Windows was telling me that my system was low on free RAM (which comes to me as a surprise as I rarely go over >6GB of usage). I looked in Task Manager and saw that the JVM was using (wait for it...) 4GB of my RAM (in total 89% of my RAM was in use). So the memory leak appears to be in 1.5.2 too it seems. I haven't tested the 13w17a snapshot yet, I hope it's been fixed there, along with the poor FPS issues, which were only partly fixed in 1.5.2.

Edit: forgot to mention I was running Minecraft under Java 6 (1.6.0.41).

I can confirm too that this bug has returned in 1.5. I've had a few of my cows escape their farms. It's even worse when some of them suffocate and die.

I am too having this issue, not sure how to fix it, a Google search doesn't help. It can't be a duplicate of MC-2067 either. That issue states that going full screen causes only a brief black screen, whereas this issue states a crash. When it crashes in full screen, the game freezes, creating a false impression of your system locking up, and you have to hold CTRl-ALT-DEL to get back to the desktop (this is assuming you're in Windows like me), From there on, there's that Windows crash message for the JVM (Java SE Platform Binary has stopped working).

Windows 7 Ultimate x64
Java 7 Update 17 x64 (I also tried JDK 6 Update 43, and that worked for a while, but the crashing started to happen again a day later)
LWJGL 2.8.4
Intel Core i5 3570K
AMD Radeon HD 7870

I get this a lot in single player survival when using enchanted tools that break blocks quickly. I find that the most common way of running into this very annoying bug is by using a diamond shovel enchanted with effficiency IV on some dirt blocks. This bug still occurs in 1.5.1 too.

Confirmed in 1.4.3 SSP survival. I haven't tested ender/single chests though.