Modpack Monster won't work on MacBook Pro

[giftkartoffel]

My friends have a server going and they just switched it to Monster. I have a MacBook Pro and have never had any issues with the various other modpacks they've decided to use, but this one just will not work. The first time I tried to launch it, it stayed on the Mojang screen for well over 30 minutes going from "not responding" to working, back and forth. The last thing the log said was:

1. 2013-12-24 17:29:33 [SEVERE] [Chisel] Skipping event FMLInitializationEvent and marking errored mod Chisel since required dependency Autoutils has errored

before I closed it. Right now it still says "Application not responding" and the log has just stopped. I don't know what to do or why it won't work for me. It's really frustrating. Please help if you can - and please actual help and not just snarky comments about my having a MacBook Pro.

 

[lavarthan]

Is the MacBook pro 64bit? If so then install the latest 64bit Java, at the moment that is Java 7 update 45, then allocate more than 1GB in the launcher. If the MacBook is 32bit then unfortunately you will be unable to run the pack as is. You can disable some of the mods, but that might mean that you are unable to connect to the server unless the server disables those mods as well. The new 1.6.4 packs need at least 2+GB and 32bit has a hard maximum allocation of 1GB.

 

[mailleseraph]

Fellow mac user here, lavarthan's suggestions are good. I would also suggest looking at the thread sticky about JVM arguments. Update JLWGL and make sure you have the right configs. The usual suspects for this sort of things. If that doesn't help, try uninstalling FTB and reinstalling(down to fresh directories and the like) and try rebooting your computer. I find especially on my mac, the memory problems inherent in java tend to cause weird memory deallocation problems even after java is closed. Restart is the easiest way to clear these problems.