Worlds keep developing a freezing problem

[MongrelVigor]

Title:

Worlds keep developing a freezing problem​

Launcher Version:

Forge 10.13.4.1448​

Modpack:

Custom​

Modpack Version:

Custom​

Log Link:

​

Details of the issue:

I had a healthy world for a long time. A certain time after I installed Rotarycraft/Reactorcraft and Applied Energistics the game started to freeze for 5 seconds, then unfreeze for 5 seconds, back and forth.

I have plenty of ram, the problem comes on suddenly and it's made 3 worlds unplayable at this point.

I've tried adjusting the amount of memory. When F3 is used I see the memory keep going from about 70% to about 85% FREEZE, then start again.

Interestingly, if I load a bad world, then later load a good world (without closeing minecraft out) the "good world" performs wrong as well.

I've tried a handful of JVM arguments I saw online. I tried AE2 and RotaryCraft.

These are the mods I use:

applied energistics 2
bdlib
buildcraft
buildcraft compat
chickenchunks
claysoldiersmod
codechickencore
cofhcore
draonAPI
Electricarft
enetbridge
fastcraft
forestry
galacticraft core
galacticraft planets
gendustry
generators
industrialcraft2
micdoodleCore
MineFactoryReloaded
neiaddons
neiintegration
notenoughitems
openblocks
opembodslib
optifine
pressure
railcraft
reactorcraft
rotarcraft
sapmanpack
thermaldynamics
thermal expansion
thermal foundation
WR-CBE​

 

[Reika]

"Spikes" of freezing are almost certainly the GC (garbage collector). Check the memory usage with F3. Does it drop down once per spike? If so, it is indeed the GC, and you need to either allocate more RAM or reduce your RAM usage.

 

[MongrelVigor]

Thank you, Reika.
Yes. It freezes around 85% then drops down to 70%

As per your reccomendation I've changed some ram settings. I went from about 2.5 gigs allocated (out of 4) to using this java argument I found reccomended online.

-Xmx3G -Xms3G -Xmn768m -XX:+DisableExplicitGC -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+UseNUMA -XX:+CMSParallelRemarkEnabled -XX:MaxTenuringThreshold=15 -XX:MaxGCPauseMillis=30 -XX:GCPauseIntervalMillis=150 -XX:+UseAdaptiveGCBoundary -XX:-UseGCOverheadLimit -XX:+UseBiasedLocking -XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=15 -Dfml.ignorePatchDiscrepancies=true -Dfml.ignoreInvalidMinecraftCertificates=true -XX:+UseFastAccessorMethods -XX:+UseCompressedOops -XX:+OptimizeStringConcat -XX:+AggressiveOpts -XX:ReservedCodeCacheSize=2048m -XX:+UseCodeCacheFlushing -XX:SoftRefLRUPolicyMSPerMB=10000 -XXarallelGCThreads=10

Now it drops all the way to 62%, then counts up (more slowly) to 81% and the freeze is a fraction of a second, instead of around five seconds.

It seems like this has made the problem much more managable, but hasn't removed it. The same oddity of the problem (memory leak?) persisting in any loaded world once a "bad world" has run still exists. Including brand new worlds with no machines etc. Interesting.

 

[Reika]

2.5 gigs allocated (out of 4

Depending on your pack, that may be nowhere near enough (I allocate 4.5GB for my pack). If your motherboard supports it, I strongly recommend getting more RAM. You can get 2GB for like $20 now, so a couple 2G sticks or one 4G stick (make sure to get the right kind for your board!) would help a great deal.

 

[MongrelVigor]

Thank you