Greetings, Repeated class retransformation can cause lambda invokedynamic call sites to be linked again, generating additional hidden lambda proxy classes. These classes are defined with STRONG_LOADER_LINK, preventing them from unloading independently of their defining class loader. Consequently, obsolete proxy classes accumulate across retransformation cycles, causing continued class-count and HotSpot Metaspace growth when the class loader remains alive. For built-in class loaders, that means for the lifetime of the JVM.
The problem is independent of the instrumentation mechanism that triggers retransformation. It can be reproduced without a third-party agent by repeatedly starting and stopping JFR recordings with method tracing enabled, while executing methods containing lambda call sites. The fix introduces a necessary condition for lambda proxy classes to be defined with STRONG_LOADER_LINK: the caller class has not been redefined/retransformed. The reproducers, before-and-after comparisons, and improvements are all detailed in the JIRA issue. Testing: - Tier 1 - 6 - Newly introduced test LambdaClassUnloading repeated 400 times. --------- - [x] I confirm that I make this contribution in accordance with the [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). ------------- Commit messages: - test adjustment - test - 8392362 Changes: https://git.openjdk.org/jdk/pull/33921/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=33921&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8392362 Stats: 151 lines in 5 files changed: 149 ins; 0 del; 2 mod Patch: https://git.openjdk.org/jdk/pull/33921.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/33921/head:pull/33921 PR: https://git.openjdk.org/jdk/pull/33921
