Recurrent Complex

Recurrent Complex

35M Downloads

Recurrent Complex seemingly causing memory leaks, which causes crashes and chunk corruption

Dimentive opened this issue · 11 comments

commented

Crash report: https://pastebin.com/raw/HW40jng3

(Also happened a few days ago: https://pastebin.com/raw/t3EyndV3)

The first time this happened, I was pregenerating chunks with Chunk-Pregenerator, and this crash did not cause world corruption, but when the crash happened today, it caused world corruption.

Every time my friend loads a certain chunk, it causes world corruption again. Looks like a corrupted chunk.

Alongside Recurrent Complex, the crash report also tells me that Biomes o’ Plenty is one of the suspected mods.

Minecraft version: 1.12.2
Forge version: 14.23.5.2781
Modpack: Enigmatica 2 (version 1.62, latest)
Recurrent Complex version: 1.4.7
Biomes o’ Plenty version: 7.0.1 (latest)

commented

I tried to delete the corrupted chunk or chunks using the Chunk-Pregenerator mod.
I used this command: /pregen delete deleteRadius square b431 b1102 15 0, which deleted 900 chunks around the specified block coordinates (X: 431, Z: 1102). However, when I went to the waypoint, I got timed out as before, and my server got a similar crash again (crash report).

Looks like my world is just completely broken. 😕

commented

This is probably mostly ReC's fault. It means that java doesn't have enough space, but ReC has a tendency to load too many structures if the world is old. See #353 .

commented

It’s not an old world, and my world’s reccomplex-structuredata.dat file for the overworld dimension is 31.1 MB.

Also, my friend can join the game just fine after we restored to a backup, but when he goes back to the chunk he was in, he is timed out again, and the server freezes.

It looks like one or more chunks are corrupted, and I’m trying to delete them with Chunk-Pregenerator.

commented

... huh? Can you send me the corresponding file?

commented

reccomplex-structuredata.dat

(GitHub doesn’t support data files, so I uploaded it to MEGA.)

commented

Cool, thanks, I'll check it out. Can you tell me the chunk / coordinates that would be affected?

commented

I don’t know the exact coordinates of the corrupted chunks; however, they are close to these block coordinates:
X: 431
Y: 63
Z: 1102

commented

Try deleting the structureGenerationData file, like mentioned before.

commented

I can’t find a file of that name. Do you mean reccomplex-structuredata.dat, like you mentioned in #353?

I will try that and see if it works.

commented

I deleted reccomplex-structuredata.dat, and it actually worked. The chunks weren’t corrupted. Everything works fine now. Thank goodness! I should’ve just tried that from the beginning. [cue self-facepalm 🤦‍♂️] Thank you so much for letting me know about this workaround!

Anyway, while heading to the chunk that was previously broken due to the structure data file while simultaneously generating new chunks around it. I got a bunch of “Error trying to emulate vanilla decoration” errors in the console: https://pastebin.com/raw/jsFEp3Nb
It’s the same error as I reported in #374, although they are still appearing with a brand new structure data file. Also, that time, I didn’t give you the full error which I got in addition to the two-line errors, as I either missed it or didn’t get it last time.

I’m very glad I solved my problem, though, after hours of fiddling with Chunk-Pregenerator and MCedit. I feel pretty stupid for not trying this simple thing first.

Anyway, this will probably happen again at some point in the future, so I wish you the best of luck in fixing this bug. Also, do you know what the “Error trying to emulate vanilla decoration” erorrs are all about? I see them relatively frequently when generating new chunks.

commented

@Dimentive the vanilla decoration error looks like this issue #336