Memory Leak on 2.2.1-a-1.21.1
Distant Horizons will crash the game when trying to build a LOD on a world
https://mclo.gs/dd6ivXN
12 Replies
Steps to recreate error:
1. Pre-generate a single player world using Chunky and Big Globe.
2. Join the world with Distant Horizons.
3. To save LOD data from the pregenerate chunks, turn distant generator on and set it to PRE-EXISTING ONLY.
4. Java will run out of memory.
I'm using a world generation mod called Big Globe but the big world size still shouldn't mean java crashes because of inadequate memory
im using the garbage collection flags
The reason I don't use distant generation to pre-generate the world in the first place is because Big Globe has it's own world-building engine built in that doesn't work well with DH
Can you replicate this with just dh nightly and big globe?
I am using a full release from modrinth but are you saying I should try using a nightly build?
Yes
is there any steps on the git on how to compile the jar?
See #links-n-downloads
ok ive got the 2.3.0dev ill test now and get back in a few hours cuz i gtg
also reading the logs before the crashes the world would slow down a lot and keep getting laggier until it would crash
Alright!
do you think the problem would be that i set the cpu load to “i paid for the full cpu”? i think the lod builder was over scheduling tasks and the cpu couldn’t keep up. I am going to rq change the cpu load to moderate
It's still a bug even if "I paid for the whole cpu" is active.
cpu load is actually set to custom on the dev build so idk
using dev version fixed the issue it seem,s
Nice! That means the next full release will fix the leak