Closed Balakay420 closed 2 years ago
This is because WorldgenProviderAccessor
specifies remap = false
in the invokers (I'd assume because they're only expected to run on a development environment), however MemoryLeakFix tries to apply all remaining mixins at one point in order to be sure the caches can be safely cleared, and therefore Mixin fails to find those methods in production.
A potential fix would be to allow those to be remapped, or to remove those mixins from the production jar or set them to not apply on production (via a mixin plugin for example).
Can confirm this issue is still present. @Hugman76 @fxmorin
This issue still exists on the 1.18 branch and in 1.18.2 (which is where it was reported to exist in the first place)
I've already moved on to 1.19. I don't do updates on earlier versions than the latest one. But, as the 1.19 version is not published yet and the fix is a very tiny change, I will re-open this ticket and push a fix for 1.18.2 when I start working on my mods again (currently on a break until ~25th of June)
Thank you for continuing to support 1.18.2 and porting the fix back. I look forward to it.
Okay, hopefully that does it
What happened?
Compatibility issue with MemoryLeakFix(https://www.curseforge.com/minecraft/mc-mods/memoryleakfix)
Fabric API version
fabric-api-0.53.4+1.18.2
Relevant log output