FAWE commands stop working: unable to create native thread: possibly out of memory or process/resource limits reached
SecretlyJealous opened this issue ยท 6 comments
Server Implementation
Paper
Server Version
1.20
Describe the bug
When a player cleared their plot the console spammed errors and all worldedit related commands stopped working for players. The server continues to run but worldedit basically stops functioning.
Log: https://mclo.gs/QDKRdnE
I was not able to use the debugpaste command because of this.
To Reproduce
- Not sure
Expected behaviour
WorldEdit commands should still work
Screenshots / Videos
No response
Error log (if applicable)
No response
Fawe Debugpaste
Unable to use fawe commands when this occurs
Fawe Version
FastAsyncWorldEdit-Bukkit-2.10.1-SNAPSHOT-818
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
Your OS doesn't allow the minecraft server process to create more threads. That typically comes down to a rather restrictive limit. We can't really do anything about that, but you can configure FAWE to create less threads if you have that limit for a specific reason and want to stick with it.
Your OS doesn't allow the minecraft server process to create more threads. That typically comes down to a rather restrictive limit. We can't really do anything about that, but you can configure FAWE to create less threads if you have that limit for a specific reason and want to stick with it.
Oh I've never had to mess with that before, the limit is currently: 513611 (I used cat /proc/sys/kernel/threads-max to check this value) and it's not something I've ever touched. Is this limit too low?
That limit sounds reasonable. I'm not sure if it applies to all threads created during the lifetime of the process or only the ones currently alive. In the case of the latter, there might be some other plugin/functionality causing too many threads to be created. In that case, creating a thread dump using jstack might be insightful.
I believe there is a "per process" max threads, unsure if that could be different configuration. Usually it's a currently running limit though. I think I had this issue a long time ago (not related)
Guessing this hasn't occurred again? Not sure it was explicitly an FAWE issue. FAWE does create a few threads but likely it coincided with a couple of other rare things going on with the OS
Guessing this hasn't occurred again? Not sure it was explicitly an FAWE issue. FAWE does create a few threads but likely it coincided with a couple of other rare things going on with the OS
It has not occurred since, I'll mark this issue as closed since I don't think it's related to FAWE