Possible memory use regression in 9.1.0-rc-1

The problem

Issue gradle/gradle#34691 (closed, 54 comments): ### Current Behavior We have a CI job that configures (by using --dry-run) almost all tasks in a fairly large build (1.6k+ leaf projects) including ones which are usually only executed locally to verify that there are no breakages due to configuration cache incompatibilities. This job takes about 3 minutes when a revision for which build cache is prepopulated is being built on Gradle 9.0.0. After switching to Gradle 9.1.0-rc-1 to evaluate compatibility of our build with the new version that job started timing out after 20 minutes.

What to do

[big-guy (maintainer)]: The configuration-cache memory thrashing on the second cache miss in a row was fixed in PR 34884. erdi confirmed it no longer reproduces on nightly 9.1.0-20250904115944. Use a build containing PR 34884 or newer.

In the GitHub issue gh:gradle/gradle#34691 (https://github.com/gradle/gradle/issues/34691), the problem reported was: Issue gradle/gradle#34691 (closed, 54 comments): ### Current Behavior We have a CI job that configures (by using --dry-run) almost all tasks in a fairly large build (1.6k+ leaf projects) including ones which are usually only executed locally to verify that there are no breakages due to configuration cache incompatibilities. This job takes about 3 minutes when a revision for which build cache is prepopulated is being built on Gradle 9.0.0. After switching to Gradle 9.1.0-rc-1 to evaluate compatibility of our build with the new version that job started timing out after 20 minutes. The verified resolution was: [big-guy (maintainer)]: The configuration-cache memory thrashing on the second cache miss in a row was fixed in PR 34884. erdi confirmed it no longer reproduces on nightly 9.1.0-20250904115944. Use a build containing PR 34884 or newer.