-
Bug
-
Resolution: Fixed
-
P4
-
8, 11, 17, 18, 19
-
b02
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8283588 | 18.0.2 | Roman Kennke | P4 | Resolved | Fixed | b02 |
JDK-8293079 | 17.0.6-oracle | Ravi Reddy | P4 | Resolved | Fixed | b01 |
JDK-8283678 | 17.0.4 | Roman Kennke | P4 | Resolved | Fixed | b01 |
JDK-8293080 | 11.0.18-oracle | Ravi Reddy | P4 | Resolved | Fixed | b03 |
JDK-8284129 | 11.0.16 | Roman Kennke | P4 | Resolved | Fixed | b01 |
However, this seems bogus, because that unnecessarily keeps ClassLoaders and all its classes alive much longer than necessary: as soon as a ClassLoader (and all its classes) become unreachable, there is no point in retaining the stuff in OSC's caches.
This can be demonstrated by compiling the attached .java files, and run:
java TestObjectStreamClass
- backported by
-
JDK-8283588 ObjectStreamClass caches keep ClassLoaders alive
- Resolved
-
JDK-8283678 ObjectStreamClass caches keep ClassLoaders alive
- Resolved
-
JDK-8284129 ObjectStreamClass caches keep ClassLoaders alive
- Resolved
-
JDK-8293079 ObjectStreamClass caches keep ClassLoaders alive
- Resolved
-
JDK-8293080 ObjectStreamClass caches keep ClassLoaders alive
- Resolved
- duplicates
-
JDK-8199589 ObjectStreamClass does not provide a mechanism to clear the cache
- Closed
- relates to
-
JDK-8283276 java/io/ObjectStreamClass/ObjectStreamClassCaching.java fails with various GCs
- Resolved
-
JDK-8280041 Retry loop issues in java.io.ClassCache
- Closed
-
JDK-8278065 Refactor subclassAudits to use ClassValue
- Resolved
-
JDK-8199589 ObjectStreamClass does not provide a mechanism to clear the cache
- Closed
- links to
-
Commit openjdk/jdk11u-dev/118ec617
-
Commit openjdk/jdk17u-dev/7d132f5e
-
Commit openjdk/jdk18u/76e25e64
-
Commit openjdk/jdk/8eb453ba
-
Review openjdk/jdk11u-dev/869
-
Review openjdk/jdk17u-dev/210
-
Review openjdk/jdk18/117
-
Review openjdk/jdk18u/36
-
Review openjdk/jdk/6375