Unable to quit/infinite loop during save after client fails to connect

[Kuratius]

I've searched existing issues and couldn't find a duplicate.

• I confirm this is not a duplicate.

Operating System

linux

Server Software Version/Commit

Pumpkin 0.1.0-dev+1.21.9

What happened?

CTRL+C fails to quit the server after a client was kicked due to a protocol error.
The server just gets stuck trying to save in an infinite loop and the process has to be killed.

To Reproduce

Connect with a minecraft client version 1.21.9 or 1.21.10 (in my case with the simply optimized modpack, though I dont believe this matters), wait until you get kicked, then try to stop the server.

Expected behavior

I'd expect quitting and saving to always succeed.

[JunkyDeveloper]

What I know, it came with the new chunk PR

[vyPal]

The problem is again a deadlock. The server sometimes manages to get into a deadlocked state when the player has to be kicked due to an error, and since the server tries to do a safe shutdown (save player and world data), it says that it's saving the world, but never actually gets around to doing it as it reaches the deadlock and gets stuck as well. The reason why it prints anything at all is because the shutdown listener runs in a separate task.

[Snowiiii]

Is this fixed ?