XCompWiz / Mystcraft-Issues

Issue tracked and localization repo for the MInecraft mod Mystcraft
xcompwiz.com
31 stars 22 forks source link

Cascading Worldgen Lag error #246

Open kaosjr opened 6 years ago

kaosjr commented 6 years ago

On the latest version (1.12.2-0.13.4.03), when running a server, the log is spammed with FML warnings telling me to report this issue to this issue tracker. Upon launching a server, it seems to work properly, but I get this warning every few seconds for different chunks: [22:37:39] [Server thread/WARN] [FML]: Mystcraft loaded a new chunk [272, -1] in dimension -2147483648 (Mystcraft) while populating chunk [271, -1], causing cascading worldgen lag. [22:37:39] [Server thread/WARN] [FML]: Please report this to the mod's issue tracker. This log can be disabled in the Forge config. It does this for different chunks every few seconds which is quite annoying due to the log spam. Here's a link to the log, but it's on GDrive because the paste is too big for Pastebin to handle. https://drive.google.com/open?id=1_K3evA8XDfmbCDgt6SpYUHg3HG_ZVYRH Here's my mod list as well. https://pastebin.com/kHNz3TNh

InjuredWolf commented 6 years ago

It's during the profiling stage, it's fine to ignore. Let the profiling run before you play, is my advice EDIT: Usually the cascading world gen is not Mystcraft's fault, either. It mentions mystcraft because that is the mod doing the worldgen at the time (for dimension -2147483648) because of the profiling, but it's using world gen from other mods/vanilla within that, which is causing a cascade

Recorpse commented 6 years ago

I'm having this issue too but my server crashes after a this has been spammed a few times

EDIT: doesn't look like its crashing anymore but every now and then between these spammed messages another message shows up about world gen. seems like its taking ages. not sure whats happening

ghost commented 6 years ago

I don't usually like to be a "me too" person, but I ran into this getting so bad it triggered my test server to shut itself down while a player was exploring a Mystcraft world. Attached the crash log in case it's of any usefulness.

crash-2018-10-17_16.05.26-server.txt

CandiceJoy commented 6 years ago

Still exists in 1.12.2

harrislapiroff commented 4 years ago

I'm also getting this. Is there any way to debug which combination of mods is causing the error short of guess and check? (I also understand Mystcraft may not be at fault here, but this doesn't seem to happen when loading overworld chunks. What makes the difference?)

Veovis-Muaddib commented 4 years ago

(I also understand Mystcraft may not be at fault here, but this doesn't seem to happen when loading overworld chunks. What makes the difference?)

As an example, RedPower 2 used to generate marble on stone that is exposed to air, and it would then have a chance to spread to other nearby exposed stone. But by design, a Cave World or Skylands age contains a lot more exposed stone than in the Overworld. So there would be no opportunities for the marble to be blocked off naturally, and it would attempt to spread so far your computer would run out of resources.

Mystcraft at its core is about customizing dimensions, most of them notably different from the Overworld. If a mod attempts to generate content in an age but makes assumptions that are only safe in the Overworld, the only way for Mystcraft to truly prevent that sort of issue would be to not let you make anything that you couldn't find in the Overworld, and at that point why bother?

Is there any way to debug which combination of mods is causing the error short of guess and check?

Generation issues like this are difficult to track down without cranking up logging or attaching a debugger. My suggestion would be to copy your instance and cut half the mods. If it goes away, then use the other half. If it doesn't go away, cut it in half again.

If the issue is a single mod, you should be able to find it in around 8 iterations even with a huge modlist.

harrislapiroff commented 4 years ago

@Veovis-Muaddib Ah ha, that makes sense. Thanks for explaining!