All modpacks take really long to load up

[John5505]

When I try to load up any modpack it takes insane amounts of time for them to load up. One modpack with 50 mods took 30 minutes. Another modpack with 152 mods took an hour and thirty minutes. I don't think the problem is ram or processor power because I always gave the modpacks at least 4 GB ram and I have an i7 processor. Could anyone help me with this? Also I didn't know where to post this because it encompases both technic official and non-official modpacks. If I should post it elsewhere let me know.

Edited September 1, 2015 by John5505

[AetherPirate]

Reduce launcher ram to 3gb, giving it lots more is counter-productive. 

Do you have other things running while you are launching things? AV scans? Lots of browser tabs? Calculating pi? 

[John5505]

I Changed the ram to 3 GB and closed everything else, the problem is still there.

[AetherPirate]

What java do you have? If it's old, update to the latest 64 bit version, and remove all others. 

[EvilOwl]

Is the loading stage take this long or is it the file downloads?

[John5505]

I set the java to the 1.8.0 x64. The problem is after the download finishes. There is no change, it starts fast, freezes, and then continues at a crawl.

[AetherPirate]

Click the option to show the console while it loads. Let's see if anything interesting is happening there. 

[EvilOwl]

I need a test done, please minimize the window when the pack starts to load and measure the time.

[John5505]

I set it so I could see the console. The most recent text before it freezes is below. Last time I measured the time it took close to an hour and a half.

http://paste.ubuntu.com/12247316/

Mod edit: spilled log moved to paste.ubuntu.com

Edited September 1, 2015 by bochen415

[AetherPirate]

Try the "minimize the window" test Bochen415 requested. 

[John5505]

The window will not minimise.

Also, all modpacks seem to freeze after this line:

Removed 0 missing texture stacktraces. Tada!

Edited September 1, 2015 by John5505

[EvilOwl]

What modpack was that on those screenshots above? Can you go to that modpack's page in the launcher, hit the "modpack options" setting, push the "Open" button, locate the config directory and go inside, find the "splash.properties" file, open that file with notepad (or similar) and change "enabled=true" to "enabled=false", then save the file,exit and re-check the game? Does that make any difference apart from the loading bars not being visible?

[John5505]

Not really.

[EvilOwl]

We need the entire latest log from .technic/logs because we're navigating blind here. Upload it to paste.ubuntu.com and post the link

[John5505]

Ok here is the log.

http://paste.ubuntu.com/12247866/

Edited September 1, 2015 by John5505

[John5505]

Any idea what the problem is?

[AetherPirate]

Disable anything else that's running, firewalls, AV, whatever. I'll look at that monster log file later. 

Edited September 1, 2015 by AetherPirate

[EvilOwl]

Very strange I'm thinking now like:

1. disable liteloader loading bars in ./technic/modpackname/liteconfig/liteloader.properties (change "loadingbar=true" to "loadingbar=false")

2. open up your intel gpu configuration and change your v-sync settings to be controlled by the application (not forced on or forced off), no hint there since I don't own any intel gpus.

Report any findings