Mac bugs and fixes September 21 2026: Chrome lag
Chapters
TL;DR
Chrome extensions on macOS were loading slowly on September 21, 2026, and Google was aware of the bug, according to 9to5Google on September 21, 2026. No Chrome fix, affected version, or formal workaround had shipped in that report. macOS 27 Golden Gate had already shipped with extensive security fixes, but it requires Apple silicon.
- Google knew about the slow Chrome extension loading, 9to5Google reported on September 21, 2026.
- No Chrome version or shipped fix was named by 9to5Google on September 21, 2026.
- macOS Golden Gate 27 fixes 210 vulnerabilities, SecurityWeek reported on September 15, 2026.
- macOS 27 requires an Apple M1 chip or newer, Ars Technica reported on September 16, 2026.
What broke on Mac on September 21?
The direct answer is that Chrome extensions were taking too long to load on macOS, while Google knew about the problem, according to 9to5Google on September 21, 2026. The report describes loading that should take a couple of seconds but does not identify the affected Chrome release or macOS build.
Google had not shipped a fix by 9to5Google's September 21, 2026 report.
The 9to5Google account from September 21, 2026 does not provide an exact delay, a list of affected extensions, a setting change, or a formal workaround for the slow loading. It also does not say whether every extension is affected. Those gaps matter because I cannot tie the failure to a named Chrome build or promise that reinstalling Chrome, clearing data, or changing an extension setting will help.
For Mac known issues, an acknowledgement is useful but incomplete without a release number and remedy. My position is that ordinary users can act on vendor release notes. The honest status from 9to5Google on September 21, 2026 is acknowledged and unfixed.
Which fixes have already shipped?
macOS Golden Gate 27 addresses 210 vulnerabilities, SecurityWeek said on September 15, 2026.
SecurityWeek's September 15, 2026 report says the fixes cover more than 90 platform components, including AppleKeyStore, Authentication Services, Foundation, Safe Browsing, Sandbox, Security, TCC, and WebKit. It also says macOS 26.7 patches 153 unique CVEs, including 26 kernel defects that could cause memory corruption, privilege escalation, system termination, or information leaks.
The Register counted 204 macOS 27 security vulnerabilities on September 15, 2026, while describing more than 260 CVEs across Apple's operating systems, browsers, and other products. Itnews Com described the macOS total as over 200 on September 15, 2026 and said some security fixes were backported to earlier supported releases.
The published totals therefore differ, but every cited account agrees that macOS 27 carries a large security repair set. SecurityWeek said on September 15, 2026 that Apple mentioned no exploitation in the wild, while The Register said the same day that none was listed under active exploitation. My detailed companion report covers the macOS Golden Gate 27 security fixes.
| Release | Reported security coverage | Source and date |
|---|---|---|
| macOS Golden Gate 27 | 210 vulnerabilities | SecurityWeek, September 15, 2026 |
| macOS 27 | 204 security vulnerabilities | The Register, September 15, 2026 |
| macOS 27 | Over 200 vulnerabilities | Itnews Com, September 15, 2026 |
| macOS 26.7 | 153 unique CVEs | SecurityWeek, September 15, 2026 |
Which Macs can install macOS 27 Golden Gate?
macOS 27 Golden Gate requires an Apple M1 chip or newer, Ars Technica reported on September 16, 2026.
Ars Technica's September 16, 2026 review says Golden Gate is the first macOS release since the mid-2000s that runs on no Intel Macs. It says Apple dropped the remaining 2019 and 2020-era Intel Macs that could officially run macOS 26 Tahoe, six years after the Apple silicon transition began.
That hardware boundary changes what an update can solve. An eligible Apple silicon Mac can take the security repairs in macOS 27. An Intel Mac cannot use macOS 27 as its update path, according to the Ars Technica requirements published on September 16, 2026.
The same Ars Technica review says Apple Intelligence now defines Golden Gate and that the former control for disabling Apple Intelligence and deleting its downloaded models is gone. That is not the Chrome extension fix. It is a separate change that a person should understand before installing the release. The cost of moving to macOS 27 can include altered settings and software behavior, while an Intel Mac faces a hard compatibility limit.
Is a Chrome extension fix coming in macOS 27.2?
No Chrome-extension fix was linked to macOS 27.2 by 9to5Google on September 21, 2026.
AppleInsider reported on September 16, 2026 that the first macOS 27.2 developer beta was available for testing after the milestone releases. Its report does not connect macOS 27.2 to Chrome extension loading or name a Chrome repair.
AppleInsider also warned on September 16, 2026 that early beta software has a higher chance of containing buggy, broken, or potentially harmful elements and should run on secondary or spare hardware. Installing macOS 27.2 beta on a work Mac is therefore not a source-backed remedy for the Chrome problem.
A point release often carries refinements, but no cited report says macOS 27.2 fixes the extension delay. Google owns the browser defect according to 9to5Google's September 21, 2026 account, and no named Chrome build with a correction appears there. I will not convert an available beta into a promised macOS update fix.
What can a Mac user do today?
SecurityWeek advised users to update promptly in its September 15, 2026 macOS Golden Gate 27 report.
On an eligible Apple silicon Mac, I would install macOS 27 Golden Gate for its shipped security repairs after checking that required work software is compatible. Ars Technica's September 16, 2026 requirements limit the release to an Apple M1 chip or newer, and SecurityWeek's September 15, 2026 report attributes 210 vulnerability fixes to the release.
For slow Chrome extensions, I would allow extra loading time or move an urgent task away from the affected extension. The cost is delay or a disrupted workflow. I would not claim that reinstalling Chrome, clearing browser data, or disabling security controls fixes the problem because 9to5Google supplied none of those remedies on September 21, 2026.
I would not put the macOS 27.2 developer beta on a daily work Mac merely to chase the Chrome issue. AppleInsider warned against using early betas on mission-critical or daily-driver hardware on September 16, 2026, and it did not name a Chrome fix. For the preceding day's status, see Mac bugs and fixes September 20 2026.
Frequently asked questions
Has Google acknowledged the slow Chrome extensions on macOS?
Yes. 9to5Google reported on September 21, 2026 that Google was aware of the Chrome bug causing extensions to take too long to load on macOS.
Has a Chrome fix shipped?
No shipped fix was named in 9to5Google's September 21, 2026 report. The report also did not identify an affected Chrome version, macOS build, or formal workaround.
Does macOS 27 run on Intel Macs?
No. Ars Technica reported on September 16, 2026 that macOS 27 Golden Gate requires an Apple M1 chip or newer and supports no Intel Macs.
Should I install the macOS 27.2 developer beta for the Chrome problem?
No cited source connects macOS 27.2 to the Chrome extension bug. AppleInsider warned on September 16, 2026 that early betas belong on secondary or spare hardware rather than mission-critical or daily-driver devices.