-
Bug
-
Resolution: Fixed
-
P4
-
11, 17, 18, 19
-
b07
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8283589 | 18.0.2 | Roman Kennke | P4 | Resolved | Fixed | b02 |
JDK-8283679 | 17.0.4 | Roman Kennke | P4 | Resolved | Fixed | b01 |
JDK-8284131 | 11.0.16 | Roman Kennke | P4 | Resolved | Fixed | b01 |
*) The cache cannot disambiguate between cleared SoftReference and the accidental passing of "null" value; in that case, the retry loop would spin indefinitely;
*) If retry loop would spin several times, every time discovering a cleared SoftReference, it would create and register new SoftReference on the ReferenceQueue. However, it would not *drain* the RQ in the loop; in that case, we might have the unbounded garbage accumulating in RQ;
WIP: https://github.com/openjdk/jdk/pull/7092
- backported by
-
JDK-8283589 Retry loop issues in java.io.ClassCache
- Resolved
-
JDK-8283679 Retry loop issues in java.io.ClassCache
- Resolved
-
JDK-8284131 Retry loop issues in java.io.ClassCache
- Resolved
- relates to
-
JDK-8309688 Data race on java.io.ClassCache$CacheRef.strongReferent
- Resolved
-
JDK-8277072 ObjectStreamClass caches keep ClassLoaders alive
- Closed
- links to
-
Commit openjdk/jdk11u-dev/b1f18cb2
-
Commit openjdk/jdk17u-dev/99237145
-
Commit openjdk/jdk18u/27fbc080
-
Commit openjdk/jdk/cebaad1c
-
Review openjdk/jdk11u-dev/887
-
Review openjdk/jdk17u-dev/244
-
Review openjdk/jdk17u-dev/245
-
Review openjdk/jdk18u/46
-
Review openjdk/jdk/7092