[FspCache] Uninitialize provider upon user unmount CL:5409956 introduced CacheManager::UninitializeForProvider(). Let Service::UnmountFileSystem() be the caller of that. When the UnmountReason reason is UNMOUNT_REASON_USER, the file system (with the same mount path) will never be used again and thus, the content cache will never be used again. Thus, when the reason is UNMOUNT_REASON_USER, uninitialize the provider from the CacheManager if it was initialized. Introduce CacheManager::IsProviderInitialized() to do the pre-condition check. Do not uninitialize if the reason is UNMOUNT_REASON_SHUTDOWN because the provider will be restored upon start up. Test: browser_tests --gtest_filter=CloudFileSystemBrowserTestWithContentCache* Bug: b/330812469 Change-Id: I474f2fa5a988e7b7d930d9f634f6fefc99a85477 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5417754 Reviewed-by: Ben Reich <benreich@chromium.org> Commit-Queue: Cassy Chun-Crogan <cassycc@google.com> Cr-Commit-Position: refs/heads/main@{#1282324}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.