I have managed to reproduce this bug once again in 1.14-pre5, but it seems to require using a map, and it also prevents the user from saving or generating a crash report once the bug occurs (this has occured in pre3 and pre4 as well, but I was not certain as to the correlation). I'm going to update this bug to reflect this information.
As of 1.14-pre5, this issue appears to have been fixed on my world. Other things have cropped up, but I will make a separate bug report for those.
uploaded another launcher log from trying to run the world as it was backed up at 1.14-pre2, in 1.14-pre4.
after the initial crash and after returning and forcing a crash, I still didn't have a crash report. Attached is the launcher log.
I don't know if this is relevant, but upon discovering this bug and attempting to exit the game, I have been stuck with a "saving world" screen for over an hour.
This doesn't seem very realistic though; maybe if it were less exaggerated?
Isn't this a Pocket Edition issue?
Still occurring in 1.14.4