Pack: Direwolf20 Pack v5 (only additional mod is BeChill's TPS mod, info about it below)
Pastebin of crash: http://pastebin.com/tggyckL5
Java runtime flags: java -server -d64 -XX:+UseFastAccessorMethods -XX:+UseCMSCompactAtFullCollection -XX:+CMSParallelRemarkEnabled -XX:CMSFullGCsBeforeCompaction=1 -XX:+UseParNewGC -XX:+DisableExplicitGC -Xmx$MAXMEM -Xms$INITMEM -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalPacing -XX
arallelGCThreads=$CPU_COUNT -XX:+AggressiveOpts -jar $SERVICE nogui
Specs: AMD Opteron(TM) Processor 6272 with 16gigs of ram. 7gb of which is allocated to FTB. I also have a vanilla server running on it with only 4gb of ram allocated, and it never has a problem. Which leads me to believe it isn't a hardware issue. (though the clock speed isn't ideal for FTB - that's a conversation for a different thread)
Java 1.7 - CentOS 6.3
I have 7gbs allocated to the server, and it ran out of memory with only 3 people online. I checked the coords of the 3 players as stated in the crash reports and nothing was out of the ordinary (one was in the middle of an ocean, one was at a no-tech tree breading farm, and one was at a pretty standard base).
We've also been noticing that memory seemed to never get free'd up (using BeChill's TPS mod to monitor it - can be found here http://www.minecraftforum.net/topic/1548779-1476-ticks-per-second-v0411/).
I checked out #ftb and DreadWingKnight seemed to think the issue was with my garbage collecting, which could definitely explain things. The problem is, I don't know enough about JVM to properly debug if I have my garbage collecting messed up.
Instead of just removing the garbage collecting flags (which should help, not hurt), I was hoping someone here with more knowledge about such things can give me a hand?
I added the above flags based on the countless amount of threads in here from people asking what flags they could use. I cherry picked the ones that seemed to be the most applicable to me.
Pastebin of crash: http://pastebin.com/tggyckL5
Java runtime flags: java -server -d64 -XX:+UseFastAccessorMethods -XX:+UseCMSCompactAtFullCollection -XX:+CMSParallelRemarkEnabled -XX:CMSFullGCsBeforeCompaction=1 -XX:+UseParNewGC -XX:+DisableExplicitGC -Xmx$MAXMEM -Xms$INITMEM -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalPacing -XX
arallelGCThreads=$CPU_COUNT -XX:+AggressiveOpts -jar $SERVICE noguiSpecs: AMD Opteron(TM) Processor 6272 with 16gigs of ram. 7gb of which is allocated to FTB. I also have a vanilla server running on it with only 4gb of ram allocated, and it never has a problem. Which leads me to believe it isn't a hardware issue. (though the clock speed isn't ideal for FTB - that's a conversation for a different thread)
Java 1.7 - CentOS 6.3
I have 7gbs allocated to the server, and it ran out of memory with only 3 people online. I checked the coords of the 3 players as stated in the crash reports and nothing was out of the ordinary (one was in the middle of an ocean, one was at a no-tech tree breading farm, and one was at a pretty standard base).
We've also been noticing that memory seemed to never get free'd up (using BeChill's TPS mod to monitor it - can be found here http://www.minecraftforum.net/topic/1548779-1476-ticks-per-second-v0411/).
I checked out #ftb and DreadWingKnight seemed to think the issue was with my garbage collecting, which could definitely explain things. The problem is, I don't know enough about JVM to properly debug if I have my garbage collecting messed up.
Instead of just removing the garbage collecting flags (which should help, not hurt), I was hoping someone here with more knowledge about such things can give me a hand?
I added the above flags based on the countless amount of threads in here from people asking what flags they could use. I cherry picked the ones that seemed to be the most applicable to me.