-
Enhancement
-
Resolution: Fixed
-
P4
-
21
-
b21
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8370556 | 21.0.10 | Sendao Yan | P4 | Resolved | Fixed | master |
| JDK-8370555 | 17.0.18 | Sendao Yan | P4 | Resolved | Fixed | master |
There's a need to find out whether all cleared references associated with a queue have been delivered to that queue. This shows up in testing fairly often, with various at best indirect and not entirely reliable solutions currently being used.
We have private Reference.waitForReferenceProcessing(), which blocks if there are cleared but not yet enqueued references, waiting for the reference processing thread to process some of them. It's available to corelibs through SharedSecrets. (It's used by java.nio.Bits.reserveMemory().)
We could make it available to tests via WhiteBox.
- backported by
-
JDK-8370555 Reference.waitForReferenceProcessing should be more accessible to tests
-
- Resolved
-
-
JDK-8370556 Reference.waitForReferenceProcessing should be more accessible to tests
-
- Resolved
-
- relates to
-
JDK-8355632 WhiteBox.waitForReferenceProcessing() fails assert for return type
-
- Resolved
-
-
JDK-8344332 (bf) Migrate DirectByteBuffer away from jdk.internal.ref.Cleaner
-
- Resolved
-
-
JDK-8348301 Remove unused Reference.waitForReferenceProcessing break-ins in tests
-
- Resolved
-
- links to
-
Commit(master)
openjdk/jdk17u-dev/a64ed9d5
-
Commit(master)
openjdk/jdk21u-dev/6bf719d9
-
Commit(master)
openjdk/jdk/d8f012ea
-
Review(master)
openjdk/jdk11u-dev/3105
-
Review(master)
openjdk/jdk17u-dev/4072
-
Review(master)
openjdk/jdk21u-dev/2358
-
Review(master)
openjdk/jdk/24527