I am unaware but assuming this is a performance crash, I still wanted to share if it could be of use. Happens whenever I use "/locate Mansion", all entities freeze before kicking me out, some minutes later the server realizes it has crashed and turns off.
Description: Watching Server
java.lang.Error
at java.util.Arrays.hashCode(Arrays.java:4146)
at java.util.Objects.hash(Objects.java:128)
at afy$a.hashCode(SourceFile:178)
at java.util.Arrays.hashCode(Arrays.java:4146)
at java.util.Objects.hash(Objects.java:128)
at agc$a.hashCode(SourceFile:214)
at java.util.Arrays.hashCode(Arrays.java:4146)
at java.util.Objects.hash(Objects.java:128)
at agb$a.hashCode(SourceFile:244)
at java.util.Arrays.hashCode(Arrays.java:4146)
at java.util.Objects.hash(Objects.java:128)Attachments
Comments 2
This may affect 1.13-pre1 (os: Windows 10 x64, java: 1.8.0_25 x64)
I "converted" a 1.12 world over to 1.13, ran /locate Igloo and got the same issue as described here: server froze, I eventually got kicked out.
Going back in the same world (worlds menu showed it was a 1.13 world), I could not reproduce the bug: there still was a freeze but eventually i got told there was no igloo nearby. Further runs of the command (still targeting igloos) caused no freezing
As a side note, the world conversion took about 20 seconds, though the world is a small creative test one with few chunks generated. And i'm not playing on a toaster!
It's the server watchdog kicking in.
Please add some details about the world, is it an old 1.12.2 world loaded in 18w22c ?
Flatworld or regular ?