-
Enhancement
-
Resolution: Fixed
-
P4
-
20
-
b13
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8367529 | 17.0.18 | Goetz Lindenmaier | P4 | Resolved | Fixed | master |
In test/hotspot/jtreg/runtime/ClassUnload/:
Some tests keep objects live by using either static fields (e.g. UnloadTest.java) or print (e.g. ConstantPoolDependsTest.java).
A better solution, as suggested by David in https://github.com/openjdk/jdk/pull/11409, is to use `Reference.reachabilityFence`.
Some tests keep objects live by using either static fields (e.g. UnloadTest.java) or print (e.g. ConstantPoolDependsTest.java).
A better solution, as suggested by David in https://github.com/openjdk/jdk/pull/11409, is to use `Reference.reachabilityFence`.
- backported by
-
JDK-8367529 Use reachabilityFence to manage liveness in ClassUnload tests
-
- Resolved
-
- relates to
-
JDK-8297740 runtime/ClassUnload/UnloadTest.java failed with "Test failed: should still be live"
-
- Resolved
-
- links to
-
Commit
openjdk/jdk/5085bd5f
-
Commit(master)
openjdk/jdk17u-dev/8bdebb05
-
Review
openjdk/jdk/12552
-
Review(master)
openjdk/jdk17u-dev/3904
(1 links to)