Lucianna

As a quick fix, whenever it happens I just use NBTExplorer and the crash log to find the offending bee and teleport it 15 blocks up. It's the least cheaty way of resolving the issue afaik and has no lasting effects under most circumstances (other than letting you back into your world). Hope it helps someone

The crash report will have a header titled "-- Entity being ticked–"
Under "Details:", there's a value "Entity's Block location". It's a bit of a mess, but what you want are "Region", "Section", and "World", in that order. If you go into NBTExplorer and open the entities folder in the root of your save file, you'll see a bunch of entries titled like "r.-1.-1.mca". You'll want whatever shows up at the very beginning of the "Region" heading in the crash report. Within that, you'll see a bunch of files for the individual chunks. In "Section" it starts of "at x,y,z in x1,y1,z1". What you want are x1 and z1, those are the chunk coords and what you're actually looking for. Then, go through all the entities in that chunk and find the one that A) has the same id as the offending party (the first thing I check for cuz it's faster), and B) is at the same position ("Pos" tag).

Set its Y coord (the center one) to something like 15 blocks higher than it currently is, and you should be able to load back in fine!

As a note, you'll continue to have these issues and have to resolve it the same way every time if you hang around the area, so depending on your preferences you may prefer just killing them (or wiping them straight from the face of the earth, pretty certain just deleting them in nbtexplorer would do as such)

Okay now after fresh install I'm getting... more problems? It's now affecting 1.12.2. That makes me think it has to be an environmental issue of some sort. I'm going to run my antivirus, uninstall, reboot, antivirus, install, and see if that fixes it

I'm not getting an hs_err_pid file

Following a fresh install nothing has changed

It's doing the same thing all the way back to 18w03b or further (that's as far as the launcher goes). No problems with previous release.

I'm experiencing the same error. It isn't generating a crash report but I've attached the log.