On Fri, 10 Dec 2021 14:44:07 GMT, Kevin Rushforth <k...@openjdk.org> wrote:
> This is a P4 bug. If the priority is correct, it does not meet the criteria > to get it into JDK 18 during RDP1, as indicated in [JEP > 3](https://openjdk.java.net/jeps/3). > > If this is objectively a P3 bug, and really does need to go into JDK 18, then > you will need to close this PR and open a new pull request in the jdk18 repo. Hmm, good question. It is kind-of leaking: current implementation prevents unloading of classes that are referenced from the OSC caches, unless memory pressure is high enough to trigger soft-ref-cleaning. Does it qualify for P3 ("Major loss of function."), or even P2 ("Crashes, loss of data, severe memory leak.")? We have users hitting this problem under different circumstances, I'd say it qualifies for P3. Opinions? See: https://bugzilla.redhat.com/show_bug.cgi?id=2016930 ------------- PR: https://git.openjdk.java.net/jdk/pull/6375
