Fix script loader to use resource manager on main sequence
ExtenionUserScriptLoader was calling ChromeComponentExtensionResourceManager::IsComponentExtensionResource() on the extension file task runner. But ChromeComponentExtensionResourceManager should only be accessed on the main sequence, because LazyInitData needs BrowserProcessImpl, which must only be accessed on the main sequence (https://crbug.com/1033644). Besides, LazyInitData() was racy in the previous setup. Bug: 1113374 Change-Id: Ie1929a024213141a2ae431221e905c73134da65e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2343344 Commit-Queue: Wojciech Dzierżanowski <wdzierzanowski@opera.com> Reviewed-by:Karan Bhatia <karandeepb@chromium.org> Cr-Commit-Position: refs/heads/master@{#797942}
Showing
Please register or sign in to comment