-
Bug
-
Resolution: Fixed
-
P1
-
8u40, 9
-
b40
-
Not verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8083481 | emb-9 | Coleen Phillimore | P1 | Resolved | Fixed | b40 |
JDK-8349967 | 8u461 | Ivan Bereziuk | P1 | Resolved | Fixed | master |
AdvancedThresholdPolicy::create_mdo uses CHECK_AND_CLEAR when creating a MethodData object. If Metaspace is full, this will result in a lot of GCs, since Metaspace will return throw an OOME everytime the interpreter tries to create a MethodData.
Is is possible for the interpreter to notice that it could not allocate the MethodData and then don't allocate any more MethodData until the OOME can reach a JavaThread so the application can handle it?
Is is possible for the interpreter to notice that it could not allocate the MethodData and then don't allocate any more MethodData until the OOME can reach a JavaThread so the application can handle it?
- backported by
-
JDK-8083481 Failing to allocate MethodCounters and MDO causes a serious performance drop
-
- Resolved
-
-
JDK-8349967 Failing to allocate MethodCounters and MDO causes a serious performance drop
-
- Resolved
-
- duplicates
-
JDK-8059215 metaspace/shrink_grow/ShrinkGrowMultiJVM times out
-
- Closed
-
- relates to
-
JDK-8282172 CompileBroker::log_metaspace_failure is called from non-Java/compiler threads
-
- Resolved
-