Describe the bug
Well, when I start the Server with the given configuration firstly sometimes creating a new world wont work it'll halt at:
[STDOUT]: Initializing stronghold positions, this may take a while
[STDOUT]: Stronghold positions initialized

Furthermore when I'm able to join soon the RAM usage will sky-rocket to the maximum I specified, that being 10G.

To Reproduce
Steps to reproduce the behavior:

1. Load a server with the following mods and it will crash
2. See error

Runtime info (please complete the following information):

• OS: Linux
• Minecraft version: 1.19.2
• Mod version: 0.2.0 ver 9.9 Alpha
• Mod branch: (fill this if you are not using the default ver branches)

Crash reports / logs
https://pastebin.com/Jr4GF42c

Other mods
https://pastebin.com/a7RNTCrT

Checklist

• [ X] I am using the official version of the mod.
• [ X] I tried the latest development version but the issue persists.
• [ X] I searched for similar open issues and could not find an existing bug report on this.

It looks something like this:

Thank you for this, I sadly cant try this out because I'm renting the server. Maybe there is a possibility where the solution can be implemented in code.

Use jemalloc

On my aarch linux, I put this argument LD_PRELOAD=/usr/lib/aarch64-linux-gnu/libjemalloc.so before all the startup flags and now it does not happen

It looks something like this:

This might be related to #159 as even with NerdTo's suggestion of using jemalloc memory usage still seems to climb all be it slower, though from some brief tests it no longer goes into swap?
Im using 0.2.0 alpha 10.51 on 1.9.4

Fixed in 0235355