Open incendial opened 1 week ago
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.
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?
Steps:
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"