Windows .exe FTB crashes when creating/loading world

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

Pedro Bastos

New Member
Jul 29, 2019
9
0
0
Operating System and bit type: Windows 7 64-Bit
Java version/update and bit type: version 7, build 45, 64-bit
Launcher version: v1.3.2
Console log and crash log, pastebin.com links: Unable to use pastebin, i will put spoiler
Have you tried following the troubleshooting guide? : Yes.
GB's of memory allocated: allocated 6 GB
Description of the Issue: I am having trouble with modded minecraft. This same bug has plagued me through 3 different 1.6.4 modpacks (Horizons, direwolf20, and monster). The launcher runs fine and the mod packs launch just fine and everything loads up to the main menu but once I select my single player world and it starts loading, Minecraft crashes. It will sometimes run fine but it crashes more often than working. I have all my drivers up to date. Thanks for your time.

Hope this help.

2013-12-25 12:07:49 [INFO] [STDOUT] TConstruct Environment: Sane and ready for action. Bugs may be reported.
2013-12-25 12:07:49 [INFO] [STDOUT] Launched Version: 1.6.4
2013-12-25 12:07:49 [INFO] [STDOUT] LWJGL: 2.9.0
2013-12-25 12:07:49 [INFO] [STDOUT] OpenGL: GeForce GTX 670M/PCIe/SSE2 GL version 4.4.0, NVIDIA Corporation
2013-12-25 12:07:49 [INFO] [STDOUT] Is Modded: Definitely; Client brand changed to 'fml,forge'
2013-12-25 12:07:49 [INFO] [STDOUT] Type: Client (map_client.txt)
2013-12-25 12:07:49 [INFO] [STDOUT] Resource Pack: Default
2013-12-25 12:07:49 [INFO] [STDOUT] Current Language: English (US)
2013-12-25 12:07:49 [INFO] [STDOUT] Profiler Position: N/A (disabled)
2013-12-25 12:07:49 [INFO] [STDOUT] Vec3 Pool Size: ~~ERROR~~ NullPointerException: null
2013-12-25 12:07:49 [INFO] [STDOUT] #@!@# Game crashed! Crash report saved to: #@!@# C:\ftb\Monster\minecraft\crash-reports\crash-2013-12-25_12.07.48-client.txt
2013-12-25 12:07:51 [INFO] [STDERR] Exception in thread "Thread-0" java.lang.OutOfMemoryError: GC overhead limit exceeded
 

Attachments

  • crash-2013-12-25_12.07.48-client.txt
    31.3 KB · Views: 101

Pedro Bastos

New Member
Jul 29, 2019
9
0
0
So i tried the arguments but it resulted in this error.

Error occurred during initialization of VM
Incompatible minimum and maximum heap sizes specified
Picked up _JAVA_OPTIONS: -Xmx512M[DOUBLEPOST=1388761978][/DOUBLEPOST]
Allocating 6GB seems a little excessive, but not overly. Try adding these arguments.

So i tried the arguments but it resulted in this error.
Error occurred during initialization of VM
Incompatible minimum and maximum heap sizes specified
Picked up _JAVA_OPTIONS: -Xmx512M
 

lavarthan

New Member
Jul 29, 2019
2,437
0
0
Use the ones for the FTB launcher not the server. The launcher passes xmx itself for one reason or another and will cause this error if you pass it within the additional arguments.
 

Pedro Bastos

New Member
Jul 29, 2019
9
0
0
Use the ones for the FTB launcher not the server. The launcher passes xmx itself for one reason or another and will cause this error if you pass it within the additional arguments.

I'm sorry if this is wrong, but i used this ones (-Xms2048m -XX:permSize=256m -XX:NewRatio=3 -XX:SurvivorRatio=3 -XX:TargetSurvivorRatio=80 -XX:MaxTenuringThreshold=8 -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:MaxGCPauseMillis=10 -XX:GCPauseIntervalMillis=50 -XX:MaxGCMinorPauseMillis=7 -XX:+ExplicitGCInvokesConcurrent -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=60 -XX:+BindGCTaskThreadsToCPUs -Xnoclassgc) and this are in the FTB launcher spoiler in the JVM Arguments.
 

lavarthan

New Member
Jul 29, 2019
2,437
0
0
Sorry about that. I wonder if it might be the fact that you are setting it to 6GB. Try setting the launcher to 2GB or upping the xms to 6144m instead of 2048m.
 
Last edited:

lavarthan

New Member
Jul 29, 2019
2,437
0
0
I remembered where I saw this problem in the thread. Here is the quote that will fix it. Sorry about that.
Greg, go to windows control panel > programs > java
and remove -Xmx512m from the _JAVA_OPTIONS environment variable