Server Implementation

Paper

Server Version

1.20.1

Describe the bug

Hello everyone :slight_smile:
So, I've been using FAWE for a few weeks, but unfortunately I had to switch back to WE because FAWE was causing random crashes on my server when I use commands or teleport :/

In the photo, these are the crashes since the beginning of the month, you can see that I did 18 tests before taking the time to write this to you, I am not posting here randomly, the other 15 crash reports, are always the same, randoms using FAWE commands or having moved/teleported/disconnected after using FAWE commands.

I just spent about 2h30 doing tests by eliminating plugins that could be in conflict, but the problem... my last test was done with only FAWE as a plugin... So it's complicated to say that it's anything other than FAWE causing this.

Attached is the log + the crash report and a video.
https://pastebin.com/EB6SmBMC
https://youtu.be/JpNBpGXDbFg

Following this, I redid the test with ONLY WE, I did this for about 5 minutes (as in the video) and nothing... no crashes.

So I don't really know where to turn to find a solution, because I really like FAWE, especially since I have big changes in game to do, but using FAWE and crashing the server when there are 30- 40 players online, I don't like :/

If someone had a beginning of solution!

Thanking you!
-z-

To Reproduce

https://www.youtube.com/watch?v=i7C7wfypLUA

Expected behaviour

Read Describe the bug.

Screenshots / Videos

No response

Error log (if applicable)

No response

Fawe Debugpaste

https://athion.net/ISPaster/paste/view/d3463d18f3c4454ca13e00dde65fd184

Fawe Version

2.7.1-SNAPSHOT-548;fe33be5

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?

No response

Any further incidents/can you still replicate this?

I forgot to specify that the world where there is the problem is a ROUND world of 50,000 blocks in diameter.
I don't know if that could be the problem.

So I did some tests again.

On this 3-minute video :
https://www.youtube.com/watch?v=xWeYMqahdow

We can see that if I click with the wooden axe WITHOUT having done ANYTHING BEFORE like FAWE command, no crash worries for a long time.

This time, starting from the same place, if I make commands and do the same thing, the server crashes after 10-15 seconds.

As if it was the fact of having stored information in the clipboard.
One more video : https://www.youtube.com/watch?v=i7C7wfypLUA

I might be to dump to read today, so that's why I am asking if there were changes to the config :D

Hi, no I didn't modify "target-size: 96" is what is generated when I put the plugin ^^

Have you edited the config file? The first number here looks too high

 target-size: 96
  # Increase or decrease queue intensity (ms) [-50,50]:
  #     0 = balance of performance / stability
  #     -10 = Allocate 10ms less for chunk placement
  # Too high can cause lag spikes (you might be okay with this)
  # Too low will result in slow edits
  extra-time-ms: 0
  # Loading the right amount of chunks beforehand can speed up operations
  #  - Low values may result in FAWE waiting on requests to the main thread
  #  - Higher values use more memory and isn't noticeably faster
  #  - A good (relatively) safe way to set this is
  #  - Use 128 x GB of RAM / number of players expected to be using WE at the same time
  #  - Paper and derivatives only. (requires delay-chunk-unloads-by to be set).

Hmmm...

allow-tick-fluids: false = no crash after 15 mnts of test

allow-tick-fluids: true = crash after 15 seconds ...