Google Chrome extensions are reportedly taking too long to load on macOS devices, when they should reasonably only take a couple of seconds, due to a bug in the latest updates. Google is aware of the issue.
The report comes courtesy of PiunikaWeb, which noted a thread entry on the Chromium issue tracker divulging the issue. The issue seems to affect macOS instances of Google Chrome, rather than Windows or mobile versions. The affected extensions are reportedly taking up to 60 seconds to load, when extensions should open instantly.
Users began reporting extensions lag in Google Chrome last week, and one of the main third-party tools it seems to affect is password managers like 1Password. The credential management app offers an extremely handy Chrome extension for password autofill across any site that requires you to remember your reasonably complex password. According to the company, it’s aware that a Google Chrome update seems to be slowing extension performance.
It doesn’t seem to only affect 1Password. Some replies indicate other extensions are being affected by the bug, though it doesn’t appear to be consistent.
What seems to be causing this disparity in extension load times is mismanaged process priority on Google Chrome’s end, though that hasn’t been verified by Google. Specifically, this seems to happen on macOS 26, and for whatever reason, Google Chrome deems certain extensions a low-priority operation, effectively pushing them to the background while it diverts resources to other tasks. The result is a much longer load time for users.
Google is aware of the issue, posting a reply to the official community page. Here’s what Google’s team says:
We’re continuing to investigate this issue as a priority, and I’ve also asked the team to consider all options including if we can roll the experiment out any further. We’ll make sure to share further updates on this thread as we have them.
Some users have noted that, in the meantime, enabling the PMLoadingPageVoter flag fixes the issue. It’s worth noting that enabling/disabling flags in Google Chrome carries some risk, so please only do so with that in mind.
You’re reading 9to5Google — experts who break news about Google and its surrounding ecosystem, day after day. Be sure to check out our homepage for all the latest news, and follow 9to5Google on Twitter, Facebook, and LinkedIn to stay in the loop. Don’t know where to start? Check out our exclusive stories, reviews, how-tos, and subscribe to our YouTube channel
