The crash you are currently experiencing is actually a tad bit different from this crash. While at first glance the crash report looks a lot like the ones of the original crash, the 1.14.2 (and, sadly, as far back as 19w14b⚠️ ) crash is actually caused by something in it.unimi.dsi.fastutil.longs.LongLinkedOpenHashSet.removeFirstLong (LongLinkedOpenHashSet.java:470)
.
What's also different about this crash, or at least as far as I know, is that a villager can have a job (or even must (didn't test for that)) to trigger this crash.
EDIT: I've opened MC-153355 to address this specific crash. Please comment there with your findings.
Can confirm fixed for 19w14a. Villager now seems to prioritise looking at the player rather than working at a workplace and when removing its workstation using /fill
, the game doesn't crash either.
Not fixed in 19w13a. I'm assuming it wasn't fixed in 19w12a & b either, as I didn't test those versions, but based on this bug being in 19w11b, I don't think an attempt fix was done between 11b and 13a.
EDIT: Rewrote the title of this bug, as this one seems more fitting.
This POI illegal state crash also happens with entities, see MC-145686 (EDIT: fixed referring to wrong bug...).
This issue is most likely related to TNT and TNT minecart explosions now having a 100% drop rate, meaning that all blocks destroyed by such explosions are now dropped rather than a couple.
For me this issue has been fixed in beta 1.11.0.3.
Solution given by ChongXG works for me. Thanks a lot!
Can confirm it's crashing. Loading bar at 3/4's of the way and just quits. Uninstall and reinstall does not work. No crash log either. Specs: Intel Core i5-8250U, nVidia GeForce MX130 2GB VRAM w/driver version 398.36, 20GB RAM, Windows 10 Home version 1803 build 17134.590.
Looks like a WAI to me, as the lectern's base is its own file. Even then it's not an exact copy of the wooden planks, because it also has a red area clearly shown on the third screenshot.
Can confirm this typo (en_us.json -> line 105).
I was able to reproduce the crash once of the three times I've tested. The crash occurred on the first test. My profile has always been a Mojang/migrated account.
Attached is the crash log of the first test (
[media]). There seems to be no crash or Realms error spam occurring in the other two tests.
Can confirm fixed for 1.13-pre7 per seed and location provided. Also did some testing with other structures in the same world, which seem fine to me. Tested were mineshaft, stronghold and shipwreck. (Sorry for the double ping)
But spawn eggs are so much easier than using commands...
Hmm... Is it also possible for you to delete the complete 1.9.4 Minecraft version file and reinstall that one? If it only affects this version, it might be something that's wrong in the 1.9.4 file.
It works fine for me with Java 8 update 77. Maybe Java 8 Update 91 triggers the crash. FYI: I'm also on Windows 10 Home 1511.
You can report MCPE bugs on https://bugs.mojang.com/browse/MCPE. And please, don't spam comments...
I do think that's intended to happen, because of potion effects when using the Latin letters to offer better readability instead of being all cramped up with words that don't fit on the screen. This has been in the game for I don't know how long, so it looks like a 'Works as intended'. Oh, it's by the way the 'inventory screen', not the 'bag page'.
@Michael Wobst It has been fixed, that's why 😉
It looks like it is fixed as of 1.14.3-pre1. Quickly placing and destroying a workstation does not cause a crash. What likely changed, is that a villager now less frequently checks for whether or not a workstation is nearby compared to 1.14.2 and earlier.