smbprovider: Remove unsupported smbprovider shares from preferences Support to mount smbprovider shares was removed in chromium:3026818 but metadata for these shares is still present in the fileSystemProvider registry of users who had added them. This causes Files app to hang on startup while it waits for the shares to initialise (which is impossible). Remove these unusable shares from the registry so that they cannot cause Files app to hang and so that they don't confuse users. successfully removed, ensure Files app no longer hangs. Bug: 1254611 Bug: 504366 Test: Artificially add (via code) old smbprovider shares, watch them get Change-Id: Ia1f30de4eea9fca1c0415f543b747bce74704043 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3205338 Reviewed-by: Josh Simmons <simmonsjosh@google.com> Reviewed-by: Peter Marshall <petermarshall@chromium.org> Reviewed-by: Luciano Pacheco <lucmult@chromium.org> Commit-Queue: Josh Simmons <simmonsjosh@google.com> Cr-Commit-Position: refs/heads/main@{#930023}
ChromiumChromium 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.