-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 14
-
Component/s: core-libs
-
b33
-
Not verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8237554 | 15 | Maurizio Cimadamore | P3 | Resolved | Fixed | b07 |
| JDK-8237710 | 14.0.2 | Maurizio Cimadamore | P3 | Resolved | Fixed | master |
| JDK-8238132 | 14.0.1 | Unassigned | P3 | Resolved | Fixed | b02 |
The javadoc of MemorySegment::allocateNative mistakenly reports that the initialization state of the off-heap memory block is undefined and should not be relied upon. This is false, give that native segments are always zero-initialized.
- backported by
-
JDK-8237554 Javadoc of MemorySegment::allocateNative should state that memory is zero-initialized
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-