Enigmatica 2: Expert - E2E

Enigmatica 2: Expert - E2E

2M Downloads

Memory leak

Tawnyman opened this issue ยท 5 comments

commented

Thank you for helping us improve.

Please follow the issue template, and do not delete any part of it.
Failure to comply will result in the issue being closed.

Question or Issue

There seams to be a memory leak

Modpack Version

1.54

Additional Context

After playing for about 5-6 hours this happens

image

The lowest it go's is in the mid 80' closing and relaunching the pack gets

image

to

image

Is there anything I can update or any settings I can change to help with this?

commented

Hey o/
There are a few things you can do, the most efficient would be to use these java parameters:
-XX:+UseG1GC -Dsun.rmi.dgc.server.gcInterval=2147483646 -XX:+UnlockExperimentalVMOptions -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M

Without those parameters, allocating too much RAM can actually cause memory leaks.

I hope it helps!

Edit: If it doesn't help I'll investigate further ofc.

commented

These are what I am using at the moment when getting the leak

-Xmx9216m -Xms256m -XX:PermSize=256m -Dminecraft.applet.TargetDirectory="C:\Users\christopher\Documents\Curse\Minecraft\Instances\Enigmatica 2 Expert" -Dfml.ignorePatchDiscrepancies=true -Dfml.ignoreInvalidMinecraftCertificates=true -Duser.language=en -Duser.country=US -XX:+UseG1GC -Xmx9G -Xms4G -Dsun.rmi.dgc.server.gcInterval=2147483646 -XX:+UnlockExperimentalVMOptions -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M

If no one else is having problems like this could it be a bad install of the pack or java?

commented

Your parameters are setting allocated RAM twice for some reason. Anyway, try reducing the RAM allocated. Increasing it would probably delay the leak further, but decreasing could remove it.

commented

Dropping my ram to 6g seams to have fixed the leak Thank you very much for the help :) The twitch launcher was responsible for the ram being allocated twice as it added some of its own parameters that I missed.

commented

Glad to hear it, thanks for the update :)