DH spamming code in log causing lag over time
Also it's preventing the game from quitting worlds properly.
16 Replies
Not only have I not added anything new, I've actually removed one mod. I've got 106 days with no issues and now this after being in the nether (not for the first time) for a bit
That mod added wind, nothing important
your database has become read only, youre not the first with that problem, ive seen two other people have it. i dont think they were able to figure it out unfortunately
you could try making your database not read-only anymore (and the folders its in as well) but that didnt fix it for the other two
Maybe SQLite has a corruption detection and the drivers make the database readonly?
Maby running it through some DB fixer would fix it?
IDK if something like that exists though
It only does this sometimes, and only after I've come from the nether. Fortunately, a restart seems to fix it.
Which database? I've been actively modifying things in the instance just fine
DH.jar is not read only, and I'm not sure how anything else would begin to get permissions or instructions to do that
Oh weird that for you it is fixed with a restart
I'm talking about the SQLite files being read only
/lodstored
Single Player:
- Overworld:
.minecraft/saves/WORLD_NAME/data/DistantHorizons.sqlite
- Nether: .minecraft/saves/WORLD_NAME/DIM-1/data/DistantHorizons.sqlite
- End: .minecraft/saves/WORLD_NAME/DIM1/data/DistantHorizons.sqlite
- Custom Dimensions: .minecraft/saves/WORLD_NAME/DIMENSION_FOLDER/data/DistantHorizons.sqlite
Multiplayer:
- .minecraft/Distant_Horizons_server_data/SERVER_NAME/Will try this when it happens again
@Puhpine (GMT +2) Yeah I'm now repeatedly crashing and can't get into the world. None of these files are read only
This seems like it's 100% on DH's end. None of these files are read only, so I surmise that DH is setting them as such when the game or world is loaded.
I guess bye bye DH. It was cool, til it started crashing randomly and using all my RAM
Maybe it's because the .sqlite folder is 11.3GB!?
Darn that sucks. I have no idea why it's doing this sorry
Deleting the entire directory and allowing it to remake them helped. I left DH installed when I pregenned the world, so I'm thinking it might have been such a large file that it was having trouble finding anything with any decent speed, resulting in a time-out error that perhaps is interpreted as a read-only error?
Idk what the code looks like, but that's my best guess
I'm now sorting a memory leak using Spark, but I have no idea what I'm doing. Perhaps memory buffer could have something to do with this, since DH requires a large portion to function actively and if it runs out repeatedly it might, again cancel its processes and throw this error out of confusion. Idk.
I took a Heap Dump summary during a particularly early bout of the leak, about 15 minutes before it crashed, but I saw nothing abnormal besides the entire buffer being filled to the brim constantly. The summary shows pretty regular stuff, honestly
are you testing with the latest nightly build? if not, i recommend doing that
Will do, rn I'm designing clockwork engines for my first airship
i sure do know what that means
Chasing my... engine down... is what it means
It's going mach 5
oof
good luck lol