| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8083088 | emb-9 | Erik Helin | P4 | Resolved | Fixed | b35 |
By inserting an allocation attempt at the beginning of the loop in CollectorPolicy::satisfy_failed_metadata_allocation, there are two safepoints we might be able to avoid:
1. When a thread continues a loop after having been stalled due to a GC_locker initiated Full GC
2. When the VM_CollectForMetadata VM operation's prologue fails because a full GC has already been run just prior to the CollectForMetadata VM operation.
1. When a thread continues a loop after having been stalled due to a GC_locker initiated Full GC
2. When the VM_CollectForMetadata VM operation's prologue fails because a full GC has already been run just prior to the CollectForMetadata VM operation.
- backported by
-
JDK-8083088 CollectorPolicy::satisfy_failed_metadata_allocation can avoid some safepoints
-
- Resolved
-