When using the /locate command when logged on a 1.14.x server, the server immediately stops responding and results in a fatal crash (fatal via the console). Tested on 2 different servers. Attached 2 server crash reports.
Might be related to MC-126244
Linked issues
Attachments
Comments
migrated
Makzevu
How often do your servers crash when you use /locate?
When I performed your same test with nine repeating command blocks (seven of which were looking for features over 1000 blocks away; two of them over 4000), my tickrate goes down very far, but never crashes the server. The server crashes only when I generate chunks coupled with that. (I tested it by generating new chunks, but already generated chunks may have worked as well) I have a AMD FX-8370 processor with 2GB given to the client and no custom options given to the server or java (running both on the same machine). However, I do have java 8 update 161 instead of the default.
If you want to bypass the server crashing, edit the server.properties by changing the "max-tick-time" setting to -1 instead of 60000. This doesn't fix the lag, it just stops the server from crashing.
migrated
This is happening when the world is generated with generate-structures=false.
migrated
Sorry to disagree with the resolution... I suspected as much hence why I reported my finding in both tickets. This crashes a server/world since there is no check for generation when the locate command is executed. Who would use this command in such a world, don't know and don't care, still it can crash a server.
wobst.michael
It's already mentioned in the other ticket that with structure generation turned off, the server will be freezing completely. No need to have a separate ticket for that.
Server console output when using /locate Village:
[10:31:07] [Server Watchdog/FATAL]: A single server tick took 60.00 seconds (should be max 0.05)
[10:31:07] [Server Watchdog/FATAL]: Considering it to be crashed, server will forcibly shutdown.