This has happened twice now. Long distance teleports into ungenerated chunks causes the server to completely crash and require a forced shutdown/restart after 60s without any tick updates. Server continues to crash again when that account reconnects at the problem location. 2 fixes have worked, 1) walk/fly another account separate from the issue account over to the location of the teleport, this in turn generates the chunks and server proceeds working properly. 2) After the second crash, at a much further distance, it was discovered setting network-compression-threshold=256 to -1 (to disable) allowed the account to connect properly and allow the server the opportunity to get past the specific issue causing the crash. When the second crash happened we teleported a different user to the same coordinates (without the first account connected) and this also caused the server to crash on a completely different system. Leaving network-compression-threshold disabled caused several other issues (rendering/porting/others...) and needed to be re enabled back to 256.For the time being we are no longer allowing long range teleports.
Note : not specifically repeatable as other teleports have not caused the error, however in the 2 specific crash points both occured with the teleport.
Related issues
duplicates
Attachments
Comments
migrated
migrated
Dupe of MC-63590
migrated
After reading the details on what my post is a duplicate of I fail to see the resemblance. Yes, the server did shutdown/kill itself after 60 seconds but my report was specifically what caused it. The fact that on a fresh relaunching of the server the same player account on connection to the place where the teleport happened would cause an instant crash to all connected players. Over and Over and how it was resolved 1 time by simply walking over with an alternate account (not normally used on this server) and in the other identical situation we first had a second player try following and teleport to the same coords where the first player was crashing with the identical crash now happening and being caused by the 2nd player. iI the second case by disabling the network compression it instantly solved it. In both cases when teleporting the terrain and chunk FAILED to generate (no data in folder either) and persistently crashed over and over until resolved. Once it crashed it persistantly crashed on one of the affected players respawning in the world and would continue to do so until we resolved it with one of the above methods. I only included one of the crash logs from one of the middle crashes in the process of trying to resolve it.