JDK-8195094 : Fix type-O in "8159422: Very high Concurrent Mark mark stack contention"
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: 10
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2018-01-15
- Updated: 2018-04-05
- Resolved: 2018-01-16
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 | JDK 11 |
|---|---|
10 b40Fixed  |
11Fixed |
Related Reports
|
Relates :
|
Description
In 8159422 MmapArrayAllocator::allocate_or_null was crafted by copying MmapArrayAllocator::allocate. The call to os::commit_memory_or_exit was changed to os::commit_memory. It was forgotten to remove the string containing the error message. The string is interpreted as a bool by the compiler, effectively calling the wrong commit_memory with signature (char*, size_t, size_t, bool) instead of (char*, size_t, bool)
Comments
|