You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ac45a70
Browse filesBrowse the repository at this point in the historyBrowse files
[Windows] Keep other versions' program caches and recreate a deleted folder
Follow-ups from review of the program cache:
- Builds on different engine versions can run side by side. The first
write of a process removed the other versions' folders, so two builds
of one app kept wiping each other's cache. A version's folder is now
removed only once all of its entries and temporary files are older
than 30 days. A hit refreshes an entry at most daily, and a temporary
file is a write in progress, so a version in use keeps its folder.
- A cache folder deleted while the process runs, for example when the
app clears its cache folder, is created again by the next write.
Before, nothing reached the disk until the process restarted.
- Test engines keep no program cache. WindowsConfigBuilder and four test
helpers created engines with the default cache. The engines of a
process share one cache through the EGL display, so later tests'
engines wrote programs to %LOCALAPPDATA%\flutter_windows_unittests,
where a later run could load them instead of compiling them. A full
run of flutter_windows_unittests now leaves no folder.
- The public headers say that the engines of a process share one cache.
0 commit comments