metaspace

来源： https://stackoverflow.com/questions/35162542/outofmemoryerror-compressed-class-space

来源： https://stackoverflow.com/questions/35162542/outofmemoryerror-compressed-class-space

问题 What is the default value of MetaspaceSize for 64-bit servers? I couldn't find it in the official documentation. I'm observing that in a server JVM process, at times, the GC frequency becomes high and keeps growing. If I restart the service a few times, it returns to stable. I think its due to the JRE upgrade. JVM Heap max size is set to be 6GB but when this problem occurs, we see only 3GB heap being used. Metaspace grows by very little and is almost always full. I tried increasing the

问题 What is the default value of MetaspaceSize for 64-bit servers? I couldn't find it in the official documentation. I'm observing that in a server JVM process, at times, the GC frequency becomes high and keeps growing. If I restart the service a few times, it returns to stable. I think its due to the JRE upgrade. JVM Heap max size is set to be 6GB but when this problem occurs, we see only 3GB heap being used. Metaspace grows by very little and is almost always full. I tried increasing the

问题 Currently i am working on Spring boot 2.1 project configured with Gradle 5.2.1. But i got out of memory error when building project and could not understand the exact reason. Please find the attached log Caused by: org.gradle.cache.CacheOpenException: Could not open proj generic class cache for build file '/Users/mac/project/build.gradle' (/Users/mac/.gradle/caches/5.2.1/scripts/eajdx6l75dt1ypyljdsfupplm/proj/proj3ca90766b0adfce53d4b035e7e9dc5fe). at org.gradle.cache.internal

问题 I am running a server app on Java 8 with the below flags: -XX:GCLogFileSize=2097152 -XX:InitialBootClassLoaderMetaspaceSize=33554432 -XX:InitialHeapSize=1610612736 -XX:MaxHeapSize=1610612736 -XX:MaxMetaspaceSize=1073741824 -XX:MetaspaceSize=536870912 -XX:NumberOfGCLogFiles=5 -XX:+PrintGC -XX:+PrintGCApplicationConcurrentTime -XX:+PrintGCApplicationStoppedTime -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC -XX:+UseCompressedClassPointers -XX:

问题 When I run the following code with multiple different requests, the java metaspace is getting increased. public String applyXsltOnXml(String xmlString, String xsltInput) throws TransformerException { String result = null; try (StringReader stringReader = new StringReader(xmlString); StringWriter writer = new StringWriter()) { TransformerFactory factory = TransformerFactory.newInstance(); Transformer transformer = factory.newTransformer(new StreamSource(new StringReader(xsltInput)));

问题 Until Java 7 there was an area in JVM memory called PermGen , where JVM used to keep its classes. In Java 8 it was removed and replaced by area called Metaspace . What are the most important differences between PermGen and Metaspace? The only difference I know is that java.lang.OutOfMemoryError: PermGen space can no longer be thrown and the VM parameter MaxPermSize is ignored. 回答1: The main difference from a user perspective - which I think the previous answer does not stress enough - is that

问题 I wrote a program to simulate MetaSpace OOM. But I found that MetaSpace Size is almost always twice as big as Used MetaSpace . Why? I run my program with flag -XX:MaxMetaspaceSize=50m , the program throw OOM when Used MetaSpace reached about 25M rather than 50M, Why? 回答1: I think the following two experiment will explain what does the gap between MetaSpace Size and Used MetaSpace mean: EXP-1 : load one class per ClassLoader, I got this: EXP-2 : load five classes per ClassLoader, I got this:

问题 A java process that I'm running performs consistently well in the first hour or so that it runs. However, performance then rapidly degrades. When profiling I found that the metaspace garbage collection happened fairly frequently until the hour mark and then got out of control: I'm fairly sure I'll be able to fix this using the -XX:MaxMetaspaceSize option. However, I'd like to know more about why this behaviour might be occurring. I can't imagine why the garbage collection algorithm would