On Tue, 17 Nov 2026 21:30:11 GMT, Markus Grönlund <[email protected]> wrote:
> At least this change addresses that repeated accumulation: it preserves > `STRONG` linkage in the common case and allows subsequently generated > implementations to unload when the redefinition predicate is true and those > implementations are no longer reachable. I think the proposal is a good trade-off. No change/impact, and no extra ClassLoaderData , or most deployments. A profiler or agent that retransforms these classes many times won't cause a memory leak, it's just the original generation that remains strongly reachable. ------------- PR Comment: https://git.openjdk.org/jdk/pull/33921#issuecomment-6981317779
