java.lang.OutOfMemoryError: PermGen with java 1.8?

[daytimepanther]

I underlined after typing to make it easier to see the important stuff.

 

I have a very weird issue with an Attack of the B-Team server. So what is happening is after awhile the server crashes with the error "java.lang.OutOfMemoryError: PermGen". I thought I knew what this was and how to fix it. So I had my host add

-XX:MaxPermSize=128m

 to the launch options. They sent me back a ticket saying these were the options: 

-Xmx%CS_MEM% -XX:+AggressiveOpts -XX:+UseGCOverheadLimit -jar %CS_JAR% nogui -XX:MaxPermSize=128m

 I thought awesome now everything will work perfectly...well no because then the server wouldn't even start. So I tested on my laptop and found out that support for MaxPermSize was removed in java 1.8. So if the server is running java 1.8 how do I stop the crash? Is it related to a mod not functioning properly? But the server must not be running 1.8 because I thought PermGenSpace was gone altogther in Java 1.8? 

 

ServerLog: 

Edited December 2, 2014 by daytimepanther

[plowmanplow]

If you are getting an error indicating that you are out of permanent generation space then you are using Java <= 1.7. Java 1.8 removed that feature altogether and merged the resource allocation. You cannot get a permgen error with Java 1.8. However, B-Team is notoriously piggy about permgen. I've had to increase mine to 384m.

Edited December 2, 2014 by plowmanplow

[daytimepanther]

If you are getting an error indicating that you are out of permanent generation space then you are using Java <= 1.7. Java 1.8 removed that feature altogether and merged the resource allocation. You cannot get a permgen error with Java 1.8. However, B-Team is notoriously piggy about permgen. I've had to increase mine to 384m.

Ahah I fixed it! The server host had the MaxPermGen argument before the -jar part and it caused the server to not launch Thanks for the help though!