Infinity Evolved Crashing on pre-allocating

[Lasting]

Title:

Infinity Evolved Crashing on pre-allocating​

Launcher Version:

1.6.61​

Modpack:

FTB Infinity Evolved Skyblocks​

Modpack Version:

1.1.0​

Log Link:

​

Details of the issue:

I haven't been able to successfully load into the game yet as it goes not responding while loading step 2 of the launcher. Im running windows 10, with a 4770k, gtx 970, 16 gbs of ram. I've tried having the memory slider in the launcher settings at max, recommended and everything inbetween.

Is there anything that you guys can do to help me?

The error I get is,

"[14:17:57] [Client thread/INFO] [EnderCore]: Attempting to initialize texture error message interceptor."... right before minecraft goes not responding and loading seizes.​

 

[Wagon153]

Can we get the full log, and not just the last line? Often times, there may be information earlier on in the log that could be useful.

 

[Lasting]

edited in the log (i think) that you want.

 

[MagicMage1238]

I noticed that using too much memory will make it crash as well - you should use no more than 2 gigs....

Also noticed that Windows 10 will have both the 32 bit version and 64 bit version of Java and the launcher will only see the 33 bit... Remove Java and install only the 64 bit (offline) Java

This may fix your issue. (I didn't look at Log report, just relaying same issues I encountered when I first tried to load up modded Minecraft)

Also Note that it will still say not responding (for about a min or less) before it continues to load but that is at the very beginning.

 

[MagicMage1238]

Just looked at the log.... At the end you ran out of memory, I could be wrong but that's what it looks like. Are you changing the memory options on the launcher or in another way?

 

[Lasting]

Ok reinstalling java and I lowered the slider to 2gb.

 

[Lasting]

Just looked at the log.... At the end you ran out of memory, I could be wrong but that's what it looks like. Are you changing the memory options on the launcher or in another way?

I did fiddle with the xmx, xms memory values. What is base? so that i can change it back.

 

[Lasting]

After I made the memory changes to 2gb and my JVM arguements in the launcher are "-Xmx2048m -Xms256m -XXermSize=256m -Dminecraft.applet.TargetDirectory="C:\Users\*****\Documents\Curse\Minecraft\Instances\FTB Infinity Evolved Skyblock" -Dfml.ignorePatchDiscrepancies=true -Dfml.ignoreInvalidMinecraftCertificates=true"

Attached is also the new log. Seems to be memory still what now?

 

[MagicMage1238]

If your reinstalling Java it should revert back to default

 

[Lasting]

Very last time i launched this was the message before it crashed.

Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
Exception in thread "Client thread" [15:33:19] [Client thread/INFO] [STDERR]: [java.lang.Throwable$WrappedPrintStreamrintln:748]: cpw.mods.fml.relauncher.FMLSecurityManager$ExitTrappedException
[15:33:19] [Client thread/INFO] [STDERR]: [java.lang.Throwable$WrappedPrintStreamrintln:748]: at cpw.mods.fml.relauncher.FMLSecurityManager.checkPermission(FMLSecurityManager.java:25)
[15:33:19] [Client thread/INFO] [STDERR]: [java.lang.Throwable$WrappedPrintStreamrintln:748]: at java.lang.SecurityManager.checkExit(SecurityManager.java:761)
[15:33:19] [Client thread/INFO] [STDERR]: [java.lang.Throwable$WrappedPrintStreamrintln:748]: at java.lang.Runtime.exit(Runtime.java:107)
[15:33:19] [Client thread/INFO] [STDERR]: [java.lang.Throwable$WrappedPrintStreamrintln:748]: at java.lang.System.exit(System.java:968)
[15:33:19] [Client thread/INFO] [STDERR]: [java.lang.Throwable$WrappedPrintStreamrintln:748]: at net.minecraft.launchwrapper.Launch.launch(Launch.java:138)
[15:33:19] [Client thread/INFO] [STDERR]: [java.lang.Throwable$WrappedPrintStreamrintln:748]: at net.minecraft.la

 

[Lasting]

If your reinstalling Java it should revert back to default

Well I just went through and reinstalled java, but the JVM arguements are still the same for me. Did i not completely fresh install and mess it up?

 

[MagicMage1238]

Just checked my own log to compare.... I'm actually running 2.5 gigs - but was once told didn't need anymore than 2 gigs.

 

[MagicMage1238]

I'm not sure why you have a Perm Size - not seeing that one on mine.... I might not be able to help after all.

 

[Lasting]

what launcher are you using? I notice that yours is different.

 

[MagicMage1238]

FTB Launcher v1.4.12

 

[Lasting]

FTB Launcher v1.4.12

Hmm i just tried to download that instead of using curse client and i cant seem to get it to run. sigh.

 

[MagicMage1238]

I haven't used curse yet and don't know how it works

 

[Mattfreyer45]

Well in both of the logs it says you have about 512 mb allocated to it . That last crash is Java trying to do Garbage Collection so often that it can't handle it .

 

[MagicMage1238]

I haven't used not seen the Curse launcher so not sure how that one works compared to the FTB Launcher and I'm not sure why it is set for 512mb because he changed the max to 2 gigs

 

[mc.crab]

Where are you changing the memory allocation? This is in your last log:

-Xmx2048m -Xms256m -XX:permSize=256m -Xmx512M

removing -Xmx512M should help, you can also remove PermSize it's not needed with Java 8. 2 gigs of ram should be enough but going over 4 gig is not recommended.