Open DaFiren opened 9 years ago
Here is the crash-report: ---- Minecraft Crash Report ---- // I feel sad now :(
Time: 8/29/15 1:22 AM Description: Exception in server tick loop
java.lang.OutOfMemoryError: Java heap space
at net.minecraft.nbt.NBTTagCompound.
-- System Details -- Details: Minecraft Version: 1.7.10 Operating System: Windows 10 (amd64) version 10.0 Java Version: 1.8.0_60, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 41493024 bytes (39 MB) / 478150656 bytes (456 MB) up to 478150656 bytes (456 MB) Mod Pack: Unknown / None LiteLoader Mods: 2 loaded mod(s)
That is an out of memory error. I am not sure why you are getting it if you are allocating 5 GB of ram to it, but this line in your crash report:
Memory: 41493024 bytes (39 MB) / 478150656 bytes (456 MB) up to 478150656 bytes (456 MB)
Seems to indicate that you are not going above 456 MB.
Perhaps it's a windows 10 thing?
A friend of mine was able to play it on windows 10, and I was having the same problem on windows 8.1.
"JVM Flags: 4 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx5120m -XX:MaxPermSize=256m -Xmx512M" For some reason, the JVM flag -Xmx is set twice. First it is set to -Xmx5120m, which is 5GB. Then it is set again to -Xmx512M, which is only half of a Gigabyte (not enough to run Blightfall). I believe your problem may be that the first argument is ignored in favor of the second. But I am not really sure why the second is there.
The short version: The Launcher seems to be overwriting your memory settings with a smaller and insufficient amount of memory. I don't know why this is happening, but I don't think it is explicitly a problem with Blightfall.
I have a few things you could try if the above solution does not fix your problem but they are advanced and may risk destroying your worlds from other modpacks, so I will not post them until you report back with the results of the above recommendation.
Scratch that: I've had a talk with @CannibalVox from the Technic Launcher team and he's convinced me it's likely that your system has "environment variables" that are overriding the Technic Launcher's java arguments. @DaFiren this is relatively advanced stuff so I am not sure I can walk you through it, but please try the following:
That worked, thank you!
You're very welcome. You can close the issue now or @talonos2 can do it. Hope you enjoy Blightfall!
I hit play on the Technic launcher, Minecraft comes up and starts to load. I get into the main menu with no problems. I go into options and turn down the visual settings, back to main menu, hit singleplayer, create new world - create new world. It generates and saves a new world, then as it is loading the world it crashes and up pops the Technic launcher. I've also tried loading directly from the world it saved prior to crashing to no avail.
I have tried different versions of java, different amounts of allocated ram (up to 5GB), had the same problem in windows 8.1 and 10 and I've tried different versions of the modpack.
I have no more ideas, but maybe you guys got something for me.