Can't Launch Minecraft (Multiple Packs)

[Ashiaka]

Title:

Can't Launch Minecraft (Multiple Packs)​

Launcher Version:

FTB Launcher v1.4.10​

Modpack:

FTB Infinity Evolved 1.7 (v2.1.2) and FTB Presents Cloud 9 (v1.2.0) both are Minecraft version 1.7.10​

Modpack Version:

v2.1.2 (Infinity Evolved) and v1.2.0 (Cloud 9)​

Log Link:

http://pastebin.com/jTJm9UyV​

Details of the issue:

Can't launch Minecraft in multiple packs, haven't been successful launching it yet since moving to Windows 10.​

 

[Ashiaka]

Here's the Cloud9 crash http://pastebin.com/WnVXN2yt
and up above in the Log Link section is the FTBInfinity crash.

 

[Moasseman]

Well, the Infinity crash is very, very clear.

"java.lang.OutOfMemoryError: GC overhead limit exceeded"

You don't have enough memory allocated to it (You have 1 GB). Absolute MINIMUM I'd go with is 2GB, and it would be better to have 4+GB allocated to MC (You can change this from the launcher in the options pane)

 

[Ashiaka]

I used to get an unhandled exception error and the whole PC crashes, I disabled MagicBees and now I don't get a full PC crash, just minecraft crash (never starts all the way as you can see) I used to not even have crash logs to go back to due to MagicBees on the Infinity side of things. Trying 3GB as the setting and forcing update on the packs.
Cloud9 Result: Minecraft starts but crashes to not responding upon entry/creation of the world (local TestWorld1 creative, new world)
Infinity Result: Minecraft starts but crashes to not responding upon entry/creation of the world (local TestWorld1 creative, new world)

So, never hit my max RAM usage, never went above approximately 16% CPU usage on the i7 4690K, went to not responding multiple times during the initial launch and then not responding once I was "in" but the world wasn't up all the way yet.

 

[Moasseman]

Cloud9 Result: Minecraft starts but crashes to not responding upon entry/creation of the world (local TestWorld1 creative, new world)
Infinity Result: Minecraft starts but crashes to not responding upon entry/creation of the world (local TestWorld1 creative, new world)

New logs please

 

[Ashiaka]

FTBInfinity Crash 2: http://pastebin.com/RM1HZzRq
FTBPresentsCloud9 Crash 2: http://pastebin.com/cC58JkEQ

Here are the new logs, by the way, thanks for all the help Moasseman, it'll be great to finally get on again and do some building.

Just to reiterate, this was with 3GB allocated in the launcher options (changed from 1GB originally). As you can see Infinity is a hungry hungry hippo or there's a serious memory issue, I'll be re-seating my RAM tonight in an effort to get the other 8GB to actually show up.

 

[Moasseman]

Just to reiterate, this was with 3GB allocated in the launcher options (changed from 1GB originally).

"JVM Flags: 3 total; -Xms256M -Xmx1024M"
ARe you sure?

E: I'm pretty sure both of your issues are to do with the 1GB memory allocation to Java. If you have set it to 3GB in the launcher, it's possible that there are variables that overrule it in other places (like environment)

 

[HeroWing2]

32-Bit?
Might be a stupid question

 

[Moasseman]

32-Bit?
Might be a stupid question

Is there a 32bit Windows 10 o.o? But that OS might be part of the problem, 10 has some slight issues

Also there's no stupid questions in tech support

 

[HeroWing2]

Srry didnt knew that and i meant the Java Version Because if you install Java it happens that it automatically installs only 32-Bit But i can be wrong too

 

[Ashiaka]

64 bit, 16GB now visible, somehow the launcher works with the full 16GB visible but didn't with just 8GB (2 4GB 2133mhz sticks were visible, 2 weren't until the other day).

By the way, yes the option was set to 3GB in the launcher even though it strangely enough reads 1024 Meg there.

I manually selected the 64 bit version of java out of the 3 that were options (2 of which being 64 bit) on the launcher while having the full 16GB showing as usable when it worked after my last post.
Why I had to manually select the 64 bit version of Java I'm not sure, also why it didn't work with 8GB of ram but it does with 16GB of ram is probably irrelevant because of Java artificially limiting my environment D:

Edit: Underlined the important stuff.