[Extensions] Instantiate PermissionsManager factory early KeyedService factories should be instantiated before profile initialization is complete, and should normally be done in the `EnsureCoreBrowserContextKeyedServiceFactoriesBuilt()` methods. PermissionsManager wasn't -- in production, this didn't cause issues because other classes called into PermissionsManager as part of their setup, which resulted in implicitly creating the PermissionsManager. However, this is an implementation detail, and not guaranteed to be consistent (and isn't consistent in the experimental android-desktop build config). Register PermissionsManager's factory as part of the standard `EnsureCoreBrowserContextKeyedServiceFactoriesBuilt()` method. Bug: 356905053 Change-Id: I521120b078730a128f5224510c0b69baed95cced Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5855301 Commit-Queue: Emilia Paz <emiliapaz@chromium.org> Reviewed-by: Emilia Paz <emiliapaz@chromium.org> Auto-Submit: Devlin Cronin <rdevlin.cronin@chromium.org> Cr-Commit-Position: refs/heads/main@{#1354232}
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.