On Mon, 16 Nov 2026 19:22:36 GMT, Markus Grönlund <[email protected]> wrote:
> 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). This pull request has now been integrated. Changeset: 8ef2f5dd Author: Markus Grönlund <[email protected]> URL: https://git.openjdk.org/jdk/commit/8ef2f5dd58a42a77909639d0c04ca09ebe4cdf73 Stats: 307 lines in 7 files changed: 300 ins; 0 del; 7 mod 8392362: Lambda proxy classes accumulate after repeated class retransformation Co-authored-by: Alan Bateman <[email protected]> Reviewed-by: sspitsyn, apangin, alanb, dholmes ------------- PR: https://git.openjdk.org/jdk/pull/33921
