Shawn Clake
- mellarks
- mellarks
- America/Regina
- Yes
- No
MC-147060![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
Flying into water and then popping back out of the water with an elytra while holding down the sprint key crashes other players near me. The game completely freezes and the only fix is to reboot the game.
Note: The person flying into the water does not crash.
Note 2: The crash seems to happen as the player flying with the elytra leaves the water.
Steps to reproduce:
- Have a friend go on to a server and stand on the shoreline of an ocean looking into the ocean
- Put on an elytra and fly into the water at a fast velocity. Hold down the sprint key while doing so
- After diving into the water, turn around and while still holding the sprint key emerge from the water
- Your friends client will have crashed
Using Optimize World with Clearing Cache Completelyregenerates some chunksConverting world to 1.14 pre release 1 regenerates some chunks
Using the optimize world feature with the new clearing cache featurecompletely regenerates some chunks. The regenerated chunks seem to be few and far between, but destroyed some player built areas.
The logs seem to indicate a problem with POI mismatch.
Converting world to 1.14 pre-release 1 completely regenerates some chunks. The regenerated chunks seem to be few and far between, but destroyed some player built areas.
The logs seem to indicate a problem with POI mismatch.
There is no crash report. As the issue states, the game simply freezes and hangs until it is force closed and reopened. This means the game is not crashing cleanly and it is not outputting a stack trace into a crash log. Please reopen, thanks.
Absolutely! Thanks! I appreciate your work on this issue.
I'm not convinced this is a duplicate as it is not causing the game to crash. It is simply regenerating the chunk and moving along as if nothing happened.
Potential workaround: Delete the poi folder inside of your world folder. It stops the bug from occurring and I have not noticed any detrimental effects of doing so yet.
I have to take the opposite opinion on this one. I do not believe this is specs related, and I have two reasons for why I believe this to be the case.
First of all: we are operating on a server since the early February snapshots with 8 gigs of RAM applied to the Minecraft server, a 7700k, and a NVMe SSD. I've been clearing the cache on server load daily. That should be more than enough horsepower to keep up.
Second reason: the lighting glitch does not happen to all areas of the server. It seems to hit specific areas frequently, and not touch other areas at all. Even more weird, as the snapshots went along into the full release, different areas of the map would be hit consistently. For example, a friend of mine would have his area hit with the lighting glitch on a daily basis in February, but then in March/April snapshots, it was my area that was being hit daily while his was not getting hit very often. Since the 1.14 release, my area has yet to be hit by the lighting glitch while three people on our server have been hit with them repeatedly.
As others have stated, I can also confirm that our Spawn area is safe.
Could this have something to do with what is in the chunks or perhaps what is in the chunks in the immediate vicinity? I have seen a small but inconsistent trend where players who have lot's of chests, item frames, rails & carts, or redstone are getting hit harder than others.
My second observation is areas where players are coming and going frequently seem to get hit harder than areas where a player tends to stay and build in a confined area by themselves.