FAWE becomes completely unresponsive when someone player leaves the server
Feniksovich opened this issue · 13 comments
Server Implementation
Paper
Server Version
1.19.2
Describe the bug
When any player leaves the server FAWE stops responding to any commands for 1-2 minutes.
The bug appears irregularly, but quite often.
To Reproduce
I couldn't find specific conditions to reproduce the bug.
To reproduce the bug, one player needs to leave the server, while the other would use some FAWE commands.
Expected behaviour
FAWE shouldn't stop responding to commands after the player leaves the server.
Screenshots / Videos
Error log (if applicable)
No response
Fawe Debugpaste
https://athion.net/ISPaster/paste/view/10b1cfec608846d4b8825685f0fc875e
Fawe Version
FastAsyncWorldEdit version 2.4.5-SNAPSHOT-278
Checklist
- I have included a Fawe debugpaste.
- I am using the newest build from https://ci.athion.net/job/FastAsyncWorldEdit/ and the issue still persists.
Anything else?
The bug is really annoying :c
Is this specific to commands run from the console, or does it include those run by players on the server? Does the player leaving have a large FAWE operation ongoing when the leave the server at all?
Is this specific to commands run from the console, or does it include those run by players on the server?
Both cases affected, FAWE runs commands with a delay after player leaving.
Does the player leaving have a large FAWE operation ongoing when the leave the server at all?
I suppose not. It is likely some players are actually leave of the server during operation process. But I don't think it's true for large operations only. Any suggestions on what large operation I should to run to test?
Agree with Phoenix, this problem occurs when the player logs out of the server, and the plugin stops responding. If you do frequent re-login to the server, the plugin will not respond for a very long time
I demand a fix for this !!! Building with a terribly bad plugin is inconvenient !!!!
The output of /fawe threads would likely be very useful when this occurs
The last time FAWE stuck until the server was restarted and didn't respond to its own commands.
So here is Spark profiler report: https://spark.lucko.me/E3CJi0eQdW (with --thread *).
I believe this is caused by players leaving the server with large clipboard that need to be close/written to disk - effectively caused by #1493
I believe this is caused by players leaving the server with large clipboard that need to be close/written to disk - effectively caused by #1493
It seems to be true. Some time ago I noticed the bug reproduces much less frequently after switching from HDD to SSD (I really forgot notice this here for some reason).
@dordsor21 Should this issue stay opened or can it be closed?
