java.lang.OutOfMemoryError: PermGen space

最新推荐文章于 2024-11-03 11:01:20 发布

weixin_33998125

最新推荐文章于 2024-11-03 11:01:20 发布

阅读量92

点赞数

文章标签： java

原文链接：https://my.oschina.net/coda/blog/40158

版权

为什么80%的码农都做不了架构师？>>>

PermGen(Permanent Generation) space is reserved for long-term objects - mostly Class objects loaded by the ClassLoader. PermGen will not be garbage collected except under very special circumstances (specifically, when the ClassLoader that loaded those classes goes out of scope). This is a garbage collection optimization - if objects that we don't expect to be garbage collected are stored separately, it compacts the space where the rest of the objects are stored, which leads to less work for the garbage collector.

The PermGen is specific to VMs having generational garbage collection. If you use, say, JRockit, the "significance of PermGen" is non-existent because JRockit doesn't have that concept. I think it's important to point out that PermGen are not part of the Java specs and only an implementation detail of (quite) some VMs.

The only thing you really need to know is that PermGen space is separate from the general heap and not affected by the -Xmx VM parameter. To set a new initial size on Sun JVM use the -XX:PermSize=64m option when starting the virtual machine. To set the maximum permanent generation size use -XX:MaxPermSize=128m option. If you set the initial size and maximum size to equal values you may be able to avoid some full garbage collections that may occur if/when the permanent generation needs to be resized. The default values differ from among different versions but for Sun JVMs upper limit is typically 64MB.

Some of the default values for Sun JVMs are listed below.