RFR: JDK-8087291: InitialBootClassLoaderMetaspaceSize and CompressedClassSpaceSize should be checked consistent from MaxMetaspaceSize

Yasumasa Suenaga yasuenag at gmail.com
Wed Jun 17 14:54:48 UTC 2015

I want to continue to discuss about CompressedClassSpace and MaxMetaspace in this (RFR) thread.

>> Should I resize CompressedClassSpaceSize than to show error message?
> If you add slightly better heuristics for the setup of the CompressedClassSpaceSize flag, for example lowering the CompressedClassSpaceSize when MaxMetaspaceSize is set, then it might be less likely that you'll hit the OutOfMemoryError when the system is set up with strict overcommit settings.

I've uploaded new webrev:

This patch checkes MaxMetaspaceSize, CompressedClassSpaceSize, and

I add to check CompressedClassSpaceSize in Arguments::set_use_compressed_klass_ptrs().
If InitialBootClassLoaderMetaspaceSize is greater than MaxMetaspaceSize,
VM will fail with error message.

InitialBootClassLoaderMetaspaceSize will be set to MaxMetaspaceSize
when UseCompressedClassPointers is not set in Metaspace::ergo_initialize().



More information about the hotspot-gc-dev mailing list