From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

To create instances of 'managed' objects Gradle uses ASM to generate subtypes, and additionally creates inner classes to instantiate new instances.

The inner classes are marked as 'public' and 'synthetic'. E.g. in <https://github.com/gradle/gradle/blob/v9.0.0/platforms/core-configuration/model-core/src/main/java/org/gradle/api/internal/model/NamedObjectInstantiator.java#L154|NamedObjectInstantiator> and <https://github.com/search?q=repo%3Agradle%2Fgradle+%2F%2C+ACC_PUBLIC+%5C%7C+ACC_SYNTHETIC%2C%2F&amp;type=code|a couple of other places>.

My understanding is inner classes should always be static, where possible, to avoid memory leaks. Should `ACC_PUBLIC | ACC_SYNTHETIC` be replaced with `ACC_PUBLIC | ACC_SYNTHETIC | ACC_STATIC`?

image.png

I saw the YourKit 'Objects retained by inner class back references' inspection reports a lot of these generated classes

If those inner classes do not access something of the enclosing class, I'd agree that static would probably be better.

<https://github.com/gradle/gradle/issues/34957>

Uuuh, would be nice if that indeed fixes the classloader isolation leak