-
Bug
-
Resolution: Fixed
-
P3
-
20
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8300621 | 21 | Maurizio Cimadamore | P3 | Resolved | Fixed | b06 |
JDK-8301535 | 20.0.2 | Maurizio Cimadamore | P3 | Resolved | Fixed | b01 |
JDK-8301520 | 20.0.1 | Maurizio Cimadamore | P3 | Resolved | Fixed | b04 |
MemorySegment.allocateNative(1024, SegmentScope.auto()).scope().isAccessibleBy(Thread.currentThread()) returns false.
Similarly
MemorySegment.allocateNative(1024, SegmentScope.global()).scope().isAccessibleBy(Thread.currentThread()) returns false too.
From documentation of SegmentScope.auto(), SegmentScope.global(), the returned scope object is accessible by any thread.
Arena.openShared().scope().isAccessibleBy(Thread.currentThread()) returns false. Though shared scope documentation doesn't explicitly state accessibility by multiple threads, the result is counter intuitive
Similarly
MemorySegment.allocateNative(1024, SegmentScope.global()).scope().isAccessibleBy(Thread.currentThread()) returns false too.
From documentation of SegmentScope.auto(), SegmentScope.global(), the returned scope object is accessible by any thread.
Arena.openShared().scope().isAccessibleBy(Thread.currentThread()) returns false. Though shared scope documentation doesn't explicitly state accessibility by multiple threads, the result is counter intuitive
- backported by
-
JDK-8300621 SegmentScope.isAccessibleBy returning incorrect values
- Resolved
-
JDK-8301520 SegmentScope.isAccessibleBy returning incorrect values
- Resolved
-
JDK-8301535 SegmentScope.isAccessibleBy returning incorrect values
- Resolved