mirror of
https://github.com/flutter/flutter.git
synced 2026-02-20 02:29:02 +08:00
0bf2b707d9
This pull request is created by [automatic cherry pick workflow](https://github.com/flutter/flutter/blob/main/docs/releases/Flutter-Cherrypick-Process.md#automatically-creates-a-cherry-pick-request) Please fill in the form below, and a flutter domain expert will evaluate this cherry pick request. ### Issue Link: What is the link to the issue this cherry-pick is addressing? https://github.com/flutter/flutter/issues/179139 ### Changelog Description: Explain this cherry pick in one line that is accessible to most Flutter developers. See [best practices](https://github.com/flutter/flutter/blob/main/docs/releases/Hotfix-Documentation-Best-Practices.md) for examples `flutter widget-preview start` creates new cached build artifacts on each run, resulting in increasing disk usage after each run. ### Impact Description: What is the impact (ex. visual jank on Samsung phones, app crash, cannot ship an iOS app)? Does it impact development (ex. flutter doctor crashes when Android Studio is installed), or the shipping production app (the app crashes on launch) This can result in disk usage slowly creeping up ~50 MiB for each execution of `flutter widget-preview start`. A reboot will currently clear this build artifacts on MacOS and Linux, but not on Windows. ### Workaround: Is there a workaround for this issue? Reboot on MacOS / Linux, clear temporary files manually on Windows. ### Risk: What is the risk level of this cherry-pick? ### Test Coverage: Are you confident that your fix is well-tested by automated tests? ### Validation Steps: What are the steps to validate that this fix works? 1. Run `flutter widget-preview start --verbose` 2. Find the location of the generated `widget_preview_scaffold` in $TMP 3. Check that there's only a `cache.dill.track.dill` under `build/`. If there's a file of the form `32637b821e3cedec3d78f27cf3f3bc35.cache.dill.track.dill`, this fix wasn't successful.