[analyzer] Excessive memory consumption after updating `analysis_options.yaml` several times

[incendial]

Steps:

1. Open analysis_options.yaml
2. Change it, save and wait for reanalysis
3. Repeat several times

I think there is something leaking after the project is reanalyzed as I'm observing increased memory consumption that does not go away (and it took around 10 updates to get to 1.4GB for me):

The above result is for when I tried to prepare a repro, and the next one is one of my last observations:

On a restart the project takes ~700 MB. Also note that no other code was changed during the restarts, only the analysis_options.yaml config.

Dart SDK version: 3.5.1 (stable) (Tue Aug 13 21:02:17 2024 +0000) on "macos_arm64"

[dart-github-bot]

Summary: The user reports excessive memory consumption after repeatedly modifying and saving analysis_options.yaml. The memory usage increases significantly with each analysis, suggesting a potential memory leak in the analyzer after updating the configuration file.

[DanTup]

I can reproduce this on Flutter stable by creating a new Flutter counter app and just changing the file repeatedly. However, on Flutter master I cannot repro. It's possible this has been fixed (@scheglov did remove a ton of the old Declarations code that was consuming a lot of memory).

Are you able to test on master/bleeding edge and see if it's resolved for you too?

[KristijanZic]

I think that I'm experiencing the same issue. As soon as I open the project I notice this usage. VScode doesn't seem to ever stop analyzing.

[DanTup]

@KristijanZic if analysis really never finishes, then I think something else is probably wrong - could you file a separate issue with details?

Please also check whether it happens in a new project or only this one, (and whether it only occurs with custom_lint enabled). Thanks!

[DanTup]

@incendial were you able to test this on a version with Declarations removed to see if it solved the problem for you too? (see my comment above).

[incendial]

@incendial were you able to test this on a version with Declarations removed to see if it solved the problem for you too? (see my comment above).

Hey, not yet.