Having mods listed as in https://github.com/scotus-1/fcsp/tree/6d861029091ae20b668a8edb791701cf672a382e/mods leads to a large amount of memory usage, in what I think is tickPrecipitation involving snow and block updates.

While this is probably out of scope, some sort of protection against excessively high usage of memory would be nice.

this memory leak took way too long to find lmfao, it was fixed after disabling most sleepwarp ticking features except for random ticks

Thanks for letting me know about this issue.
I'm not quite happy with using CompletableFuture in the manner that I do with SleepWarp; there are several other issues which are cropping up because of it. I'm going to try a new approach in v3.0.0 which (hopefully) won't cause dupes and crazy memory usage.

I haven't read the codebase, but my current working hypothesis is that due to some mods such as Visual Workbench, Easy Magic, Easy Anvils, and especially Snow! Real! Magic! that make certain things into block entities or override vanilla functionality, the way the ticks are called to accelerate each block get put onto the async event loop (I read one asyncio guide like 2 years ago), and it just ends up blocking for extremely small amounts of time. However, the tick function can't be executed or throws an error somewhere and then it slowly builds up as a memory leak which then causes the GC to go haywire as well as the game making the server average 5 tps 💀 with 8gb/10 with a single player on and causing the sever to crash . I wish I could load the heap dump spark outputed in the Eclipse MAT, but it just didn't work so I don't know. I'm speaking out of my ass right now, but I think that makes sense?

Not to mention, I had to later disable random tick like crops and stuff because that still caused a leak but slower.