JDK-8185580 : Refactor Threads::possibly_parallel_oops_do() to use Threads::parallel_java_threads_do()
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 10
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2017-07-31
- Updated: 2019-05-22
- Resolved: 2017-10-17
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 10 |
|---|
10 b31Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
Currently we have 2 places where we apply the parallel claiming protocol when iterating threads, that is Threads::parallel_java_threads_do() and Threads::possibly_parallel_oops_do(). In order to avoid code duplication, the latter should call the former, using a private ThreadClosure. We already had one bug (JDK-8185273) that was caused by an inconsistency between the two.