Can confirm for 1.17, server hosted on CubedHost. Seems that it was triggered right after a player fell out of the world in The End dimension.
[29-Jul-2021 15:24:32] [INFO] <redacted_username> fell out of the world
[29-Jul-2021 15:24:33] [FATAL] Error executing task on Server
[29-Jul-2021 15:24:33] java.lang.NullPointerException: Cannot invoke "it.unimi.dsi.fastutil.objects.ObjectSet.remove(Object)" because "☃" is null
[29-Jul-2021 15:24:33] at abk.b(SourceFile:202) ~[minecraft-release-1.17.jar:?]
[29-Jul-2021 15:24:33] at abe.a(SourceFile:906) ~[minecraft-release-1.17.jar:?]
[29-Jul-2021 15:24:33] at abp.a(SourceFile:449) ~[minecraft-release-1.17.jar:?]
[29-Jul-2021 15:24:33] at acj.a(SourceFile:944) ~[minecraft-release-1.17.jar:?]
[29-Jul-2021 15:24:33] at uf.a(SourceFile:114) ~[minecraft-release-1.17.jar:?]
[29-Jul-2021 15:24:33] at uf$a.a(SourceFile:42) ~[minecraft-release-1.17.jar:?]
[29-Jul-2021 15:24:33] at pm.a(SourceFile:21) ~[minecraft-release-1.17.jar:?]
[29-Jul-2021 15:24:33] at xm.run(SourceFile:18) ~[minecraft-release-1.17.jar:?]
[29-Jul-2021 15:24:33] at aqu.c(SourceFile:151) ~[minecraft-release-1.17.jar:?]
[29-Jul-2021 15:24:33] at aqy.c(SourceFile:23) ~[minecraft-release-1.17.jar:?]
[29-Jul-2021 15:24:33] at net.minecraft.server.MinecraftServer.b(SourceFile:783) ~[minecraft-release-1.17.jar:?]
[29-Jul-2021 15:24:33] at net.minecraft.server.MinecraftServer.c(SourceFile:167) ~[minecraft-release-1.17.jar:?]
[29-Jul-2021 15:24:33] at aqu.z(SourceFile:125) ~[minecraft-release-1.17.jar:?]
[29-Jul-2021 15:24:33] at net.minecraft.server.MinecraftServer.bg(SourceFile:765) ~[minecraft-release-1.17.jar:?]
[29-Jul-2021 15:24:33] at net.minecraft.server.MinecraftServer.z(SourceFile:759) ~[minecraft-release-1.17.jar:?]
[29-Jul-2021 15:24:33] at aqu.bq(SourceFile:110) ~[minecraft-release-1.17.jar:?]
[29-Jul-2021 15:24:33] at net.minecraft.server.MinecraftServer.y(SourceFile:743) ~[minecraft-release-1.17.jar:?]
[29-Jul-2021 15:24:33] at net.minecraft.server.MinecraftServer.x(SourceFile:696) ~[minecraft-release-1.17.jar:?]
[29-Jul-2021 15:24:33] at net.minecraft.server.MinecraftServer.a(SourceFile:274) ~[minecraft-release-1.17.jar:?]
[29-Jul-2021 15:24:33] at java.lang.Thread.run(Thread.java:831) [?:?]
@Kenneth Campbell Cannot be done while the server is up. By definition the --forceUpgrade flag is a server startup option.
## Force Upgrade (1.13+) / Optimize World
#
# Possible values: true, false
# Default: false
#
# Forcefully upgrade the full world prior to the start of the server.
# This option should be disabled after the first successful run and does not automatically disable itself.
#
## It is HIGHLY recommended that you complete a backup prior to enabling this!
#
force-upgrade=false
as defined by CubedHost's .tweaks file.
Confirming logger spam and infernal lag at times. See attached
World was generated locally in version 1.14., moved to Realms 1.14.4, then moved to CubedHost in 1.15.2, and today with DIM-1 deleted it was updated directly to 1.16.1. The world was never run on any snapshot version.
The spam always triggers on server start, almost every time a player joins, sometimes on player death, and at random times.
On every occasion it caused the server 40-80 (rarely 130) ticks delay!
Problem still occurs with snapshot 18w31a. Please see attached s2_18w31a_profile-results-2018-08-01_16.58.40.txt
minecraft:cod is taking up 50.11% of CPU time, of which 41.04% is its ai > newAi > goalSelector.
In comparison zombie takes up less than 2%, so is the skeleton, creeper and any other entity. Putting it other way, the cod's logic alone is taking up equally as much as all other entities ingame combined!
@Brian Rivas can you please add 18w31a to the affected versions?
Confirming that this happens on two servers a friend of mine and I own.
It is keeping the CPU at 100%, players and mobs start experiencing extreme rubber band movement.
Server specs:
Server 1
Host: self-hosted on a VPS
CPU: Intel Xeon D-1531 @ 2.199 GHz
RAM: 8 GB
Server 2
Host: https://vahosting.net - Premium Grass plan
CPU: Intel i7-4790K, 4 cores/8 threads @ 4.0/4.4 GHz
RAM: 2 GB
See attached the debug profiler's output from the two servers mentioned above and notice the bolded values:
filename | T/s | path to entity | % of process(or) usage |
---|---|---|---|
s1_profile-results-2018-07-29_16.00.47.txt | 8.83 | levels > world > tick > entities > regular > tick > minecraft:cod | 87.72% / 67.05% |
s1_profile-results-2018-07-29_16.16.26.txt | 16.78 | levels > world > tick > entities > regular > tick > minecraft:cod | 77.87% / 42.01% |
s2_profile-results-2018-07-29_10.54.33.txt | 6.86 | levels > world > tick > entities > regular > tick > minecraft:cod | 96.32% / 80.57% |
s2_profile-results-2018-07-29_13.10.03.txt | 14.67 | levels > world > tick > entities > regular > tick > minecraft:cod | 81.87% / 57.42% |
The threads dealing with the cod (mostly the ai > newAi) are taking up the majority of the CPU time.
Can confirm using 1.19pre3 as well.
Cannot run any commands (nor switch game modes with F3+F4) or send messages from the game client.
Commands on the server console work without problems though.
The server is hosted remotely and has a different time zone configured compared to the players' clients, obviously a wide-spread use-case.