Windows 10, version 1803, build 17134.765
Intel Core i5-8250U @ 1.6GHz (boost 3.4GHz)
nVidia GeForce MX130 w/2GB VRAM
2GB RAM (Minecraft default)
Driver version 419.17
Bundled Java version (1.8.0_51)
Crash, Entities, Village system
NOTE: This bug is different from
MC-145686, but could be related. MC-145686 was about java.util.Optional.get(Optional.java:135), this one is about it.unimi.dsi.fastutil.longs.LongLinkedOpenHashSet.removeFirstLong (LongLinkedOpenHashSet.java:470) gotten in a near-similar environment.
Have a villager with a job near a workstation (preferably within a 1-block radius). Attached (Testing.zip) is the world I used. At -83 / -12 is a pit with a villager. This is where I performed my testing.
How to reproduce
To trigger the crash, one commonly needs to quickly destroy and place the workstation. This will cause the villager to quickly switch from being a nitwit and the job belonging to the workstation.
In the snapshots of 1.14, this crash seems to be fairly easy to reproduce, as the villager keeps its job for longer or even doesn't become a nitwit once its workstation is destroyed. In 1.14.2, villagers switch quickly between nitwit and having a job, thus it requires more destroying and placing (and more time to reproduce). Suggestion is, taken from the comments about this bug on
MC-145686, to map the place and destroy buttons to keys near each other, for example E and F for placing and destroying, respectively.
1.14.2 server crash log: crash-2019-05-29_16.34.45-server.txt
1.14.2 game log (anonimised): 2019-05-29-5.log
This bug has been present since at least 19w14b, but doesn't seem to be in the game in 19w14a.