-
Bug
-
Resolution: Fixed
-
P3
-
hs25
-
b40
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8020176 | 8 | Coleen Phillimore | P3 | Closed | Fixed | b98 |
Test that concurrently load classes and execute methods via reflection fails due to OOME: Metadata space, but according to GC log Metaspace is almost free.
Issue could be reproduced with 64-bit VM and -XX:+UseCompressedKlassPointers.
Test uses MaxMetaspaceSize=256m and ClassMetaspaceSize=128. After start up, test fill metaspace with generated classes and then start multiple threads, that execute JCK tests via reflection. On OOME tests unloads part of those generated classes. However, VM continue throwing "OOME: Metadata space" when all generated classes are already unloaded and according to GC log metaspace is almost empty.
Issue could be reproduced with 64-bit VM and -XX:+UseCompressedKlassPointers.
Test uses MaxMetaspaceSize=256m and ClassMetaspaceSize=128. After start up, test fill metaspace with generated classes and then start multiple threads, that execute JCK tests via reflection. On OOME tests unloads part of those generated classes. However, VM continue throwing "OOME: Metadata space" when all generated classes are already unloaded and according to GC log metaspace is almost empty.
- backported by
-
JDK-8020176 NPG: With -XX:+UseCompressedKlassPointers OOME due to exhausted metadata space could occur when metaspace is almost empty
-
- Closed
-
- relates to
-
JDK-8009562 NPG: Can run out of small Metaspace chunks in some cases
-
- Closed
-