[Bug Report]: Crash on startup on 5.0.10-1.19

[BlueCorallite]

Describe the bug; What happened?

Hi, I'm trying to use the MCDungeonsWeapons mod for 1.19.2 along with a bunch of mods but the game crashes on startup when trying to do so. I checked every mod I'm using and I narrowed it down to DungeonsWeapons as the one that causes the crash. Other mods like DungeonsArtifacts and DungeonsArmors work fine, so I'm not sure why this one is causing problems.

Here is the log if it helps. Any help would be appreciated. latest.log

Expected Behavior

Not crashing and to launch properly, I don't know what else to say.

Mod Version

5.0.10-1.19

Minecraft Launcher

Vanilla

Operating System

Windows

Modpack

No response

Additional context

No response

[chronosacaria]

🤔 Not sure why this is still happening. Thanks for reporting this. I'll look into it!

[BlueCorallite]

Of course!

[chronosacaria]

Actually, @BlueCorallite, it looks like MCDW isn't causing an issue; at least, not one that is showing up on the log. Does the crash happen without MCDW installed? I know you said you narrowed it down the MCDW, but I'm not seeing a place where it is explicitly involved with the crash

[BlueCorallite]

The game launches fine without it. When I put it in the mods folder and try again, it crashes.

[chronosacaria]

Actually, as a matter of fact, MCDW isn't loaded in that log, at all:

- mcda 2.4.4
- mcdar 1.5.3-1.19
[MCDW would be right here if it was loaded]
- mcsa 3.1.4+1.19

[chronosacaria]

Ah, okay. Could you add it and post that crash, please? That way I can see what the issue is in relation to MCDW

[BlueCorallite]

oh. lmao. Let me try again

[BlueCorallite]

latest.log This should have it.

[chronosacaria]

Okay, that's the same issue that Daedelus had. I'll have to ask LlamaLad about if this could be from the Mixin Extras update. Thanks, so much!

[BlueCorallite]

No problem, thank you

[chronosacaria]

@BlueCorallite Hey, mate, could you create a Mixin Dump for me so that I can see what is going on? If you are using the vanilla launcher, you can do this by going to your instance and clicking edit. Then, at the bottom, in the JVM ARGUMENTS section, you can add this to the end: -Dmixin.debug.export=true. This will create a dump when it crashes in the .minecraft\.mixin.out directory. If you could zip that up and post it here, that would be awesome! There is no personally identifiable information in those files, so you're safe to do so. I've added a picture so you can see what it looks like in the Edit Installation screen. The example I have is for 1.19.4, but it is the same for any other version

[BlueCorallite]

Will do

[BlueCorallite]

class.zip Is this it?

[chronosacaria]

@BlueCorallite Yep, that's perfect! Thank you!

[chronosacaria]

@BlueCorallite Could you try removing MemoryLeakFix and see if that resolves the issue?

[BlueCorallite]

Okay, I'll try

[BlueCorallite]

Huh. It works.

[BlueCorallite]

Tbh I could probably do without the MemoryLeakFix mod, but is there anyway I can still use it?

[chronosacaria]

Awesome! I'll report back. I'm definitely not going to consider this resolved because that means that there is some kind of conflict with a very, very important mod. Thanks for all of your testing!

[chronosacaria]

There is something happening with MemoryLeakFix and MCDW, which I think I know what the issue is. I'm gonna ask some of my other dev friends and see what they think

[BlueCorallite]

No problem, hope it gets fixed soon. Thank you for your help as well. All mod creators have my respect and appreciation.

[chronosacaria]

@BlueCorallite Okay, so here is something that it appears that you can do in the meantime:

Replace MemoryLeakFix version 1.0.0 with version 0.8.0. You can find it either on Modrinth or CurseForge. That seems to launch okay

[BlueCorallite]

Okay sure, I'll try it out

[BlueCorallite]

yeah, 0.8.0 seems to work. Thanks!

[chronosacaria]

No problem!