Startup Fix?

[The CobbleManiac]

Before I say anything, here's a pastebin of the launcher console so far: http://pastebin.com/VeF7p2DL

So basically what I did here was startup launcher, and I went ahead and launched the FTB Infinity Pack 3 times and it kept popping u with the same error: "Error while running launchMinecraft(): java.lang.NullPointerException". I am not sure if that was pastebinned, but hell I have no idea what does that mean.

Also, don't know if this extra info helps but... I'm running Java 7 update 75 (64 bit) on a 64 bit (duh) laptop (Processing power 1.7GHz, installed memory 4GB) and allocated 2GB RAM to minecraft FTB.

Can anyone give me a fix for this? It'll be much appreciated

 

[Hambeau]

You probably don't have enough Ram to run infinity... Most of the larger 1.7.10 packs seem to work best with these Ram settings:

Min. = 2GB
Max. = 4GB
Permgen = 256MB

These are the default settings in Java 1.8, by the way.

 

[The CobbleManiac]

Hmm I would've thought you could lower the graphics for RAM issues. Seems like another problem, RAM issues AFAIK (and experienced) just cause lag spikes, low frames and occasional crashes, not complete failure for startup. (Though I may be wrong, I ain't no computer genius =P)

Another thing is that I use Java 7, cause my computer doesn't have anywhere near enough RAM for Java 8 to function completely, so does that mean I need a stronger processor? Or more memory for the computer? Or is it a software/ program issue I'm dealing with here?

 

[rhn]

Hmm I would've thought you could lower the graphics for RAM issues. Seems like another problem, RAM issues AFAIK (and experienced) just cause lag spikes, low frames and occasional crashes, not complete failure for startup. (Though I may be wrong, I ain't no computer genius =P)

RAM have very little to do with performance and everything to do with startup/loading. What happens during startup is that the game is being loaded from your harddrive onto the RAM. If you run out of allocated RAM before the entire modpack is loaded, the startup fails and the game crashes.

The new large modpacks needs a lot of RAM("a lot of space") for them to be loaded. I would suggest sticking to some smaller or older modpacks that require less resources(they can be just as much fun IMO). That or upgrade your system. Even if you upgrade your RAM and manage to load a modpack like Infinity you are going to be hampered by your CPU I think.

 

[The CobbleManiac]

RAM have very little to do with performance and everything to do with startup/loading. What happens during startup is that the game is being loaded from your harddrive onto the RAM. If you run out of allocated RAM before the entire modpack is loaded, the startup fails and the game crashes.

The new large modpacks needs a lot of RAM("a lot of space") for them to be loaded. I would suggest sticking to some smaller or older modpacks that require less resources(they can be just as much fun IMO). That or upgrade your system. Even if you upgrade your RAM and manage to load a modpack like Infinity you are going to be hampered by your CPU I think.

Hmm does RAM issues cause complete failure of even launching the game itself? The issue I am encountering is that every time i click the launch button it the buttons become unclickable for a period of time, then they suddenly become clickable again and the game console comes out with this:

Spoiler

Logging in...
Login complete.
Checking local assets file, for MC version1.7.10 Please wait!
Setting up native libraries for Infinity 1.7 v Recommended Version MC 1.7.10
Syncing Assets:
Java Path: C:\Program Files\Java\jre7\bin\javaw.exe
Pack: Infinity 1.7 1.7.10
Setting MinMemory to 256
Setting MaxMemory to 2048
Defaulting PermSize to 256m
Error while running launchMinecraft(): java.lang.NullPointerException

So it wasn't a long string of craziness when I hit launch, it just came out with this repeatedly. No Mojang icons. Just this. This still classified as a crash?

Additional post: Just to add: I realize that this problem only starts happening for me for MC 1.7.10, 1.6.4 and below work fine for odd reasons.