[BUG] Regular crash...
aurel85 opened this issue · 9 comments
Hi,
With 1.18 there is a regular crash on my server when a new player does an claim, apparently a selection with their claim tool. Please fix this bug as soon as possible because it is really problematic...
Error : https://pastebin.com/1ATLDS17
I use the last dev version of this plugin and Paper 1.18.1.
@comonier the error come from method
RedProtect-7.7.3-b410-Universal.jar//br.net.fabiozumbi12.RedProtect.Bukkit.helpers.RedProtectUtil.addBorder(RedProtectUtil.java:88that consume way too much resources, it's why the server freeze and you see "move wrongly" errors.
ok i will check it
In the same with 1.18.2 : https://pastebin.com/bQvXWnfP
From the log it doesn't seem to be an rp problem - your server crashed after a player took a boat ride as if it didn't have enough processing power and memory for the rendering of chunks that was happening at the speed it was happening.
[14:37:11] [Server thread/WARN]: Raptyss moved wrongly!
[14:37:13] [Server thread/WARN]: Raptyss moved wrongly!
[14:37:14] [Server thread/WARN]: Raptyss moved wrongly!
[14:37:38] [Paper Watchdog Thread/ERROR]: --- DO NOT REPORT THIS TO PAPER - THIS IS NOT A BUG OR A CRASH - git-Paper-267 (MC: 1.18.2) ---
[14:37:38] [Paper Watchdog Thread/ERROR]: The server has not responded for 10 seconds! Creating thread dump
anyway are u trying to use the last 1.18.1 dev build?
@comonier the error come from method RedProtect-7.7.3-b410-Universal.jar//br.net.fabiozumbi12.RedProtect.Bukkit.helpers.RedProtectUtil.addBorder(RedProtectUtil.java:88 that consume way too much resources, it's why the server freeze and you see "move wrongly" errors.
With 1.19 version a selection limit has been added so that solves the problem, in a way.
The problem was never really resolved in the end and it persists in 1.20.4 (and in previous versions)...
Please do something because it's really unstable for new players, the server crashes quickly...
The problem stills? The method addBorder is called only by player! if you having issues with this in logs, prob someone is using a lot, or via command block/script.
Btw, any log appearing after this crash can be a false" positive, as redProtect try to listen player and mob actions all the time.
Looking into a detailed code, theres a setting region-setting > border > intensity to deny things like this. In bigger regions, render a border can cause server crash (but is rare, i cant reproduce in my server in any way with a lot bigger regions)