JDK-8209054 : ConcurrentHashTable: Do not allocate inside critical section
- Type: Bug
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 12
- Priority: P2
- Status: Closed
- Resolution: Duplicate
- Submitted: 2018-08-07
- Updated: 2019-08-15
- Resolved: 2019-01-15
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 13 |
|---|
13Resolved  |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
|
|
Relates :
|
Sub Tasks
|
JDK-8213791 :
|
|
|
JDK-8214310 :
|
Description
Allocation inside the critical section stops some uses-cases of this hash-table. The down side with moving allocation to caller is that a insert might have bigger chance to fail and thus more often allocate/free might be called.
Comments
|