Crash log:
step to produce:
1. load normal MC server
2.set /gamerule spawnRadius 5000 or higher
3. die to mobs 5-10 times until respawn button doesnt work. server should then time u out
3.5. if u stay off server and look in task manager you will notice excessive cpu usage refering to a memory leak, this will not stop until someone logs in.
4. login back in server and server should instantly crash with this log error.
i dont know if this can be re-created in single player.
i also do play the server on same machine as client - working on setting up server for friends
Related issues
duplicates
Comments
CubeTheThird
migrated
whats odd is in f3 mode TX number runs from 1-20 never going above 20, but i dont know how to check tick rate cuz there is no command for it like how forge has it.
Set max-tick-time in server.properties to a value higher than 60000 or to -1
if i used -1 the server had massive memory leak with excessive cpu usage. the map im using is only 20k blocks wide and 10k block height.
i dunno why this bug is flagged as resvoled/fixed which its not lol, and im ONLY one on the server.
Duplicate of MC-63590. The server is effectively shutting itself down because it is lagging too much. See that report for details.