External extension warning takes too long to appear on Windows |
|||||
Issue descriptionChrome Version : 54.0.2840.99 (Official Build) m (32-bit) URLs (if applicable) : https://www.skype.com/en/download-skype/skype-for-windows/downloading/ What steps will reproduce the problem? (1) On Windows, download SkypeSetupFull.exe and run the installer package (2) Complete the installation steps What is the expected result? The external extension prompt ("Another program has added an extension...") should appear in the Chrome menu soon after the installation is completed. What happens instead? User #1: The prompt didn't appear for a long time. Approx. 48 hours. User #2: The prompt also didn't appear immediately, but it appeared after re-starting Chrome.
,
Dec 11 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 11 2017
,
May 15 2018
,
Jun 15 2018
We use base::win::RegKey::StartWatching to observe registry changes for this, wonder why it won't trigger. Since this is an observer, it is not guaranteed to be called *immediately*, but again it shouldn't take 48 hours. Some further thought: if the observer registration fails, there should be a warning "Error observing HKLM/HKCU" [1], do they appear in the logs? [1] https://cs.chromium.org/chromium/src/chrome/browser/extensions/external_registry_loader_win.cc?type=cs&sq=package:chromium&g=0&l=235
,
Jan 18
(5 days ago)
I'm going to archive this for now, as I've seen these warnings appearing momentarily after adding some external extension, but didn't notice any significant delay. Of course there can be some edge cases, and without a repro, it's hard to act on the bug. Reopen if you run into the issue w/ repro. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ajha@chromium.org
, Dec 3 2016Labels: M-54