I have noticed the java process the FTB launcher is running under sometimes goes crazy and burns all the CPU time it can along with memory up to the max allowed. At that point I can kill the FTB client and it solves the performance problem. The minecraft instance runs perfectly fine then as it is running under a different java process. The FTB launcher is not doing a whole lot at that point so there is no reason for it to be consuming that kind of CPU and memory - other than if it is caught in an infinite loop somewhere or something due to a bug somewhere in the code.
As a workaround is there an option to automatically shutdown the FTB launcher after it starts the MC instance? I'm not really sure why it continues to run in the background once it starts up the minecraft instance anyway - it is not needed at that point.
As a workaround is there an option to automatically shutdown the FTB launcher after it starts the MC instance? I'm not really sure why it continues to run in the background once it starts up the minecraft instance anyway - it is not needed at that point.