| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8195581 | 11 | Goetz Lindenmaier | P3 | Resolved | Fixed | b01 |
| JDK-8197722 | 10u-cpu | Goetz Lindenmaier | P3 | Resolved | Fixed | master |
| JDK-8200945 | 10.0.2 | Unassigned | P3 | Resolved | Fixed | b01 |
| JDK-8195932 | 10.0.1 | Goetz Lindenmaier | P3 | Resolved | Fixed | b01 |
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)
- backported by
-
JDK-8195581 Fix type-O in "8159422: Very high Concurrent Mark mark stack contention"
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8159422 Very high Concurrent Mark mark stack contention
-
- Resolved
-