-
Bug
-
Resolution: Fixed
-
P2
-
17, 21, 22
-
b15
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8317786 | 21.0.2 | Aleksey Shipilev | P2 | Closed | Fixed | b03 |
The DirectByteBuffer.Deallocator is run via a Cleaner which, in turn, is run in a separate thread. This means the deallocator must be thread-safe. However, this is not the case as it does not adhere to fundamental safe-publication rules and modifies its internal state with normal memory semantics.
- backported by
-
JDK-8317786 (bf) Concurrency issue in DirectByteBuffer.Deallocator
-
- Closed
-
- relates to
-
JDK-8324972 (bf) Make DirectByteBuffer.Deallocator idempotent
-
- Closed
-
-
JDK-8325173 JDK-8316337 causes double-free in Cleaner code
-
- Closed
-
- links to
-
Commit openjdk/jdk21u/f2cb058b
-
Commit openjdk/jdk/cf74b8c2
-
Review openjdk/jdk21u/231
-
Review openjdk/jdk/15784
(2 links to)