❗ Checklist

• I am using the official english version of Slimefun and did not modify the jar.
• I am using an up to date "DEV" (not "RC") version of Slimefun.
• I am aware that issues related to Slimefun addons need to be reported on their bug trackers and not here.
• I searched for similar open issues and could not find an existing bug report on this.

📍 Description

server crashed

error: https://mclo.gs/3rRGEww

I reported it to the ajLeaderboards plugin, and it said that the problem is not with it but with slimefun

" your server is running out of threads, and it appears that Slimefun is using the most threads (162). ajlb is using 70 "

📑 Reproduction Steps

I don't know how it happened but the server crashed

💡 Expected Behavior

that doesn't happen

📷 Screenshots / Videos

No response

📜 Server Log

No response

📂 /error-reports/ folder

No response

💻 Server Software

Purpur

🎮 Minecraft Version

1.20.x

⭐ Slimefun version

https://prnt.sc/PnU70Fb6nTaT

🧭 Other plugins

No response

I reported it to griefPrevention, and they also said that the problem is with slimefun:

griefPrevention: https://prnt.sc/39yg_jPj5djv

I reported it to griefPrevention, and they also said that the problem is with slimefun:

that screenshot is completely unrelated to this issue?

I reported it to griefPrevention, and they also said that the problem is with slimefun:

that screenshot is completely unrelated to this issue?

OK, I'll open another report

there was no need to open a duplicate issue, instead just provide evidence of what happened.

my bad

there was no need to open a duplicate issue, instead just provide evidence of what happened.

only the server crashed before restarting, and this error appeared that the server's memory had run out, but I have 21GB on the server in use.

this spark I did before because the TPS was dropping, so I reported it to griefPrevention, and they pointed me to slimefun

spark: https://spark.lucko.me/krvm0xoPyb

same issue as #4011

Few things to mention from your spark report
Networks addon is causing 11% due to the vanilla pusher https://spark.lucko.me/krvm0xoPyb?hl=88775 which of the 11% 5% is caused by griefpreventions module in dough so this issue #4117

isitemsimilar is also doing 0.5% https://spark.lucko.me/krvm0xoPyb?hl=86563 which is quite high for my liking

then there is also 0.66% taken by supreme setting a charge https://spark.lucko.me/krvm0xoPyb?hl=104832
No clue why its that high, it looks like a BS call but that should just be to memory and not to file soo /shrug need to look into it more.

Why your server crashed i cant really tell its hard to find it, we do use a lot of threads since we try to multi thread a lot or in the minecraft world asynchronize a lot

@SrMonsterYT do you have any logs from before the server crashed?
are you with any hosting providor or do you self host?

okay so i assume you manage it your self. There should be some logs in the dmesg that should give some more info about this. You could always limit the pusher but i would initially wait for the dough PR to be merged. This would save a lot from your timings

all the logs are like this, there's nothing else, I even reported it to griefPrevention, and everyone pointed only to slimefun

I am pretty sure you havent checked the kernel logs.
You can use dmesg to view that.
Slimefun is known to use a lot of threads but that shouldnt matter much.
We need info on why your server crashed and your kernel could give us more info.
You are self hosting this so please check the logs.
Not minecraft server logs, kernel logs.

i mean its easy to point you to somewhere else and say they are the issue but we need more info.
You are the first to report this in ages so it might be something not Slimefun there are 2134 servers running Slimefun and 1 reported this issue.
So it can be something else entirely.

Few things to mention from your spark report Networks addon is causing 11% due to the vanilla pusher https://spark.lucko.me/krvm0xoPyb?hl=88775 which of the 11% 5% is caused by griefpreventions module in dough so this issue #4117

isitemsimilar is also doing 0.5% https://spark.lucko.me/krvm0xoPyb?hl=86563 which is quite high for my liking

then there is also 0.66% taken by supreme setting a charge https://spark.lucko.me/krvm0xoPyb?hl=104832 No clue why its that high, it looks like a BS call but that should just be to memory and not to file soo /shrug need to look into it more.

Why your server crashed i cant really tell its hard to find it, we do use a lot of threads since we try to multi thread a lot or in the minecraft world asynchronize a lot

@SrMonsterYT do you have any logs from before the server crashed? are you with any hosting providor or do you self host?

it's a dedicated server, i9 10k, 128gb, i'm not hosting it's bought from a company, there's nothing before the glitch just that, players do a lot of farming and use the pusher a lot, if there was something to replace the pusher it would be perfect.

okay so i assume you manage it your self.
There should be some logs in the dmesg that should give some more info about this.
You could always limit the pusher
but i would initially wait for the dough PR to be merged.
This would save a lot from your timings

yes

Please send $ ulimit -a output

Please send $ ulimit -a output

should I type this into the VPS and send you the result?

yes

fish: Expected a variable name after this $.

type ulimit -a
$ means its a shell command

type ulimit -a

https://prnt.sc/Ua2hWTRmHLoi