JDK-8077571 : ObjPtrQueue is poorly named
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2015-04-13
- Updated: 2015-11-29
- Resolved: 2015-11-10
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 9 |
|---|
9 b94Fixed  |
Related Reports
|
Blocks :
|
|
|
Blocks :
|
Description
The ObjPtrQueue is strongly tied to the SATBMarkQueueSet, and is only used for SATB support. And with recent changes to the handling of the contents of these queues to support eager reclaim of humongous objects, it is no longer true that the queue elements are always valid oops - they can be stale references to reclaimed humongous objects (and maybe eventually even stale young gen object references). So the present class name and comments about it always containing oops should be changed. SATBMarkQueue would be consistent with the set name.