One of the worlds I generated used the server software would cause memory leak issues on linux. It would use more memory than allocated and invoked watchdog to shut down the server the first time and caused a system-wide freeze the second time. It only happened on this specific world so far that was not logged onto by a user until the second time.I've attached the world, crash report, and anything else I found that may be relevant.
The startup flags were: -jar -Xms2650M -Xmx3G
The crash report shows memory usage of 4822 MB
Attachments
Comments 8
I've noticed this issue when writing mods that create dimensions at runtime - it's common, and also reproducable on Fabric Loader 0.12.11/Minecraft 1.18.1, on dedicated server
[^crash-2021-12-12_18.06.29-server.txt]
This is repeated and only happens on certain seeds/configurations. Doesn't appear to happen on any of the three vanilla dimensions
The library used for generating these dimensions is [https://github.com/nucleoidmc/fantasy]
-XX:+ShowCodeDetailsInExceptionMessages -Dfabric.dli.config=<path> -Dfabric.dli.env=server -Dfabric.dli.main=net.fabricmc.loader.launch.knot.KnotServer are the flags used to reproduce. I'm using Eclipse Adoptium's termium JDK
Hello, we tried to reproduce it, but failed.
What are the exact steps to reproduce this issue? How long does it take until the server crashes?
Thank you 🙂
Eventhough this issue is for a server related memory leak, i've tried to bring this up for Single Player Survival as wel. Rather see some people look into that, it takes 5-10 minutes to accure but than your computer is about to crash, funny enough not the game. Allocated memory is 8gb.
Is this still a problem in 22w06a or later? If it is, please provide as much information as possible.
Please share the start-up parameters of the server. Thanks!