On Tue, 17 Nov 2026 01:48:18 GMT, Andrei Pangin <[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).
>
> src/java.base/share/classes/java/lang/Class.java line 2939:
> 
>> 2937: 
>> 2938: 
>> 2939:     // Returns whether this class or any of its superclasses has been
> 
> Why do we care about superclasses? Redefinition of a superclass (e.g. 
> java.lang.Object) does not unlink already linked call sites, does it?

It reuses existing machinery—the counter originally served as a version stamp 
for reflection caches. A cache records the count when it is built; a later 
mismatch means it must be rebuilt. Redefining a superclass also increments its 
subclasses’ counters because their reflection results can include inherited 
members. This lambda fix reuses that broader invalidation signal.

To narrow the predicate, i.e., identifying the redefine / restranformation 
status only for the immediate caller class, would mean introducing a native 
method, and probably also a compiler intrinsic, to query 
InstanceKlass::has_been_redefined().

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/33921#discussion_r4597318296

Reply via email to