Memory leak in DistantHorizons-2.3.4-b-1.21.4-fabric-neoforge?
Started generating with in on the server with 16G of RAM dedicated, it crashed after a bit and came up with a file saying out of memory error, so I tried 32G, and same thing happened, filled up my RAM to 32G dedicated and crashed soon after saying the same thing. No crash reports
45 Replies
I just have noisium, C2ME, cloth and fabric configs installed other than DH
First two I know I have the latest versions

Does it happen if DH is the only mod?
Let me check, give me a few
:eyes_sus: somehow -XX:+HeapDumpOnOutOfMemoryError was in my start.bat file
I'm going to check if that was it first...
Actually, that should just create a heap file when there's a memory error... not cause one..
Okay, it doesn't seem like it occurs with just DH... if it does it doesn't seem as drastic of a leak... was at ~7.5GB used now at 8.3GB...
Will continue running it for a few and see what happens 👍
My CPU temps are also a lot lower for balanced than before.. or even minimal impact for that matter lol
Hm... just jumped to 9.0GB
Back to 8.5 now :D
Yeah, I think it's good, it was one of the other two mods or some combo of them
Guess I'll just use DH
you can speed it up by setting
globalExecutorParallelism = 32
in the c2me.tomlYou think it was nosium then causing the issue?
no
you should add lithium though
and scalable lux
free perf
Spoke too soon
Same thing happened with just DH
maybe try updating your fabric loader to 0.17.2 and see if that helps?
Otherwise maybe try GC-flags since you have none at the moment and are trying to have the server pregenerating with 32GB of memory
16 and 32GB of memory
It was on 16, only increased it to 32 because out of memory
I'm not even sure how to update a fabric server...
I know for paper/spigot/vanilla/etc you just replace the paper-354 with paper-405 or whatever
It won't even move to the folder for some reason... Weird

Okay, I restarted my computer and now it works
Do I just reinstall it to the same folder and it'll replace everything it needs to?
You should be able to put the loader into the
.fabric/server
folder in the server folder
oh waitand delete the old one?
no need to delete the old one
So just drag and drop there and it's updated?
although you got the launcher, not the loader
Hm, I didn't see any other options unless they hid it away
my bad then, you should be able to just launch the server with that file
Okay, it's starting up, we'll see if it works with the new version of fabric 👍
Gotta let it get to 8.1%

What's strange is sometimes it does about 10-15K chunk/s while sometimes it does 100-150K chunk/s here
Looks like I drew the short straw this time
that is interesting xD
I think maybe once I load it all once, it'll do it again at 150K chunk/s
But if I restart computer (just did) and resume, it takes a lot longer
At least, that's what it seems like
thanks
Install java 25 as well and use the flags for java 25
Was about to ask that
Do you have a link for java 25?
Google "temurin java"
You can verify in the cmd via
java -version
Yay :D

I put the args in start.bat file too, let's try it now
Whoa, it started up in like 1/5-1/10 the time
and we back at 100K chunk/s

Oh, only lasted till it got to where it was the first time before updating to java 25, back at 15K/s now
Oh well, not the biggest deal in the world, will suck once I'm at 90% done though and it takes 20 hours to catch up
Whoa, only using 800-900MB of RAM currently 👀

Might be working now 🤞
Okay, I'm stopping it to add c2me, lithium, and scablelux
What does this mean?

Anything to be concerned about?
Seems like it's working still so far
-# I really hope this does not mean that your database is corrupt but instead that only that lod is corrupt
I just got another different warning:

So I'll probably have to restart either way is what I'm assuming?
Or will it just have missing chunks because of it in a few spots?
No
Just tested loading the LOD in-game after transfering it to the client, works fine 👍
Solution
I think it was the fabric version then (16.10 I think doesn't work)
Because it's still generating fine < 1GB RAM used