IssueTracker

Also reported to Gradle here

Thank you for the report. The reason for the hue GC time is that the Java VM is getting close to OOM, and will keep GC'ing to free memory.

Is this consistently happening when building your project, or only after some time? How about when running with --no-daemon, that is ./gradlew --no-daemon ... does that complete compilation?

It doesn't occur with the daemon disabled. A Gradle engineer spotted a leak in my heap dump here.

Based on the comments on the GitHub issue, this is either a Gradle or plugin issue.

Thanks for filing the issue. It seems that the metadata rule that we use in the IDE to fetch code samples is causing some issues. Are you using Ivy repositories by any chance?

Also, is Another heap dump after GC.run recorded after the build?

Are you using Ivy repositories by any chance?

I don't believe so. At least, we haven't added any manually. Any surefire way to check?

Also, is Another heap dump after GC.run recorded after the build?

Yes. Both are.

Thanks for the additional info. The issue is in the Gradle sync code. More specifically:

override fun execute(ctx: ComponentMetadataContext) {
  val id = ctx.details.id
  ctx.details.addVariant(SAMPLE_SOURCE_CLASSIFIER) {
    attributes {
      attribute(Category.CATEGORY_ATTRIBUTE, getObjects().named(Category.DOCUMENTATION))
      attribute(DocsType.DOCS_TYPE_ATTRIBUTE, getObjects().named(SAMPLE_SOURCE_CLASSIFIER))
    }
    withFiles {
      addFile("${id.name}-${id.version}-$SAMPLE_SOURCE_CLASSIFIER.jar")
    }
  }
}

as the action passed to addVariant captures ObjectFactory which holds Project reference causing the big leak.

Nice!

Would that be fixed in studio, AGP, or both? If AGP, would a 4.0.x release be possible?

The issue in is on the IDE side, and 4.1 and 4.2 are impacted. IDE 4.2.0-alpha08 and 4.1.1 (most likely) will contain the fix.

🎉 Thank you!

Any chance that the fix could still go into 4.1.0? The leak feels very significant and we already had to skip 4.0 because of lint issues.

I will try to push the fix in 4.1, pending our release team approval.

Thank you🤞

The fix will be included in Android Studio 4.1.0-RC1. As already mentioned in #10, Android Studio 4.2.0-alpha08 will also be fixed.