Josh O

This is marked as a duplicate of another issue, but that one is marked resolved because it's "too hard to change".... Overall, I'd say support for Minecraft's issues is fairly good, however that is coming from the Java edition. I tried playing Bedrock with my friend on mobile recently, and I am appalled by how awful this version is. Major game breaking issues are ignored and the community means nothing. The game even comes with ads built in, even though we already spent money to get it in the first place... I wasn't going to comment, but I hope someday someone actually pays attention to these problems...

https://bugs.mojang.com/browse/MCPE-19393

I have been having the issue in 18w43c as well. So far, all I've done in the version is fly around the world a lot, but the world continually fails to load in, freezing and loading a few chunks, then freezing and loading a few more, and every once in a while freezing and then loading in everything around me as expected. It continues this cycle regularly until eventually, around the time when I'd expect the world to load everything normally, the entire game simply crashes.

Edit: I tried running in Java 11 as well just to see if that would fix anything, but it didn't.

I can confirm this is still an issue in 1.13-pre release 5.
I'm not entirely sure, but it seems like it may have improved a tiny bit from 1.12.2 though.

Confirmed for 18w14a.

Sorry, I'm still trying to get the issue to happen again. It is on and off every couple weeks. I'll have the problem for a month or so, then it's just gone for the next 2 weeks, and it suddenly comes back. It's somewhat there still, but just not very severe. There is nothing unusual in the logs, but from what I can see, the display_update thread's usage rises a lot, from about 3 to 12% after moving my mouse around a lot.

Confirmed for 1.12.

Confirmed for 1.11.2.
It'd be really great if the sound engine didn't limit how many sounds could be played at once as I was building a noteblock song, but it ignores half the notes...

Java 8 update 111 fixed the issue for me.

I've seen this same bug happening on the OptiFine installer as well as the FTB Launcher's profile creation dialogue, so this is NOT a Minecraft/Mojang problem, it seems to be a general Java bug that is caused by something in dialogues.

This bug is happening on AMD and Intel CPUs as well as Intel, AMD and Nvidia graphics cards with latest and outdated drivers so I doubt it's the hardware that's the problem. Just skimming through the launcher code, I didn't notice anything strange that should cause this issue. I can't figure out what the cause is at all because I have another computer with an older graphics card and newer other hardware with an otherwise nearly identical situation for software that doesn't have the problem.

I just wanted to add that not only does the lower bar of the launcher render incorrectly, the entire launcher gets messed up once the drop down box is clicked and deleting the second profile once the bug is occurring does not solve the problem even after clicking the dropdown box again. The problem persists after COMPLETELY wiping every last trace of Minecraft from the computer and doing a fresh install as well as using the installer's "repair" feature.

After further testing, after about 5 or so seconds once the play button is correctly displaying indicating the launcher is ready to be used (or when the log displays "Logging in with access token"), the problem can activate. I haven't been able to reproduce this issue prior to those 5 seconds passing. This means the issue ALWAYS occurs once you have clicked the dropdown box, however, it may not happen visually for a couple more seconds. Then the visual bug will start happening. Something changes in that time period that causes this problem. If I waited until after the period was over and then clicked the dropdown box, it happens immediately with no noticeable delay.