Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8204438 | 11.0.1 | Kim Barrett | P4 | Resolved | Fixed | team |
OopStorage introduced a bespoke RCU-inspired mechanism in the management of its arrays of blocks (part of JDK-8200557). This mechanism was developed before GlobalCounter (JDK-8195099) was available, and has continued to be used due to a limitation of GlobalCounter (it could attempt to safepoint, due to JDK-8191798). Now that the limitation has been addressed, OopStorage should use GlobalCounter and discard its private mechanism.
- backported by
-
JDK-8204438 OopStorage should use GlobalCounter
-
- Resolved
-
- relates to
-
JDK-8195099 Concurrent safe-memory-reclamation mechanism
-
- Resolved
-
-
JDK-8191798 redo nested ThreadsListHandle to drop Threads_lock
-
- Resolved
-
-
JDK-8204179 [BACKOUT] OopStorage should use GlobalCounter
-
- Resolved
-
-
JDK-8200557 OopStorage parallel iteration scales poorly
-
- Resolved
-