If Google Chrome has been crashing, freezing, or behaving erratically on your Mac over the past few weeks, you’re not alone. Following an unusually large batch of Chrome security patches rolled out in mid-2026 — many of them identified and fixed with the help of AI-assisted vulnerability scanning — a wave of Mac users have reported new stability problems with the browser. Threads across the Apple Support Community show hundreds of Mac owners dealing with sudden tab crashes, spinning beach balls, GPU-related errors, and Chrome quitting unexpectedly right after launch.
The good news: this is a well-known, widely reported issue, and the fixes are straightforward once you understand what’s actually happening under the hood. This guide walks you through the causes, the most reliable step-by-step fixes, and additional solutions that address edge cases specific to macOS.
What Causes This Issue
The recent surge in Chrome instability on Mac traces back to how quickly Google has been shipping patches. According to public disclosures, Google closed more Chrome vulnerabilities in a single month than in the previous two years combined, largely because AI-driven fuzzing tools uncovered a backlog of memory and rendering bugs. While that’s good news for security, the accelerated release cadence has introduced regressions that interact poorly with macOS-specific components.
Users in the Apple Support Community have narrowed the problem down to a few recurring triggers:
- GPU process crashes — Chrome’s hardware acceleration layer conflicts with recent macOS graphics drivers, particularly on Apple silicon Macs running macOS Sequoia and Tahoe.
- Corrupted user profiles — Rapid patch cycles have caused some Chrome profile databases to become out of sync with the new binary, leading to launch failures.
- Outdated extensions — Extensions built against older Chromium APIs can trigger renderer crashes after security updates tighten sandboxing.
- Keychain permission mismatches — macOS occasionally revokes Keychain access after a Chrome auto-update, causing password prompts and freezes.
- Rosetta 2 conflicts — Users still running the Intel build of Chrome on Apple silicon are hitting compatibility errors.
Step-by-Step Fixes
Work through these in order. Most users in the Apple Support Community report that one of the first three steps resolves the issue completely.
- Force quit and update Chrome to the latest stable build. Open Chrome, click the three-dot menu, go to Help > About Google Chrome, and let it check for updates. If Chrome won’t launch, right-click its Dock icon, choose Quit, then reopen it. The most recent stable channel release has addressed many of the crashes introduced by the June patch wave.
- Disable hardware acceleration. This is the single most effective fix reported by Mac users. Go to Settings > System in Chrome and toggle off “Use graphics acceleration when available.” Relaunch Chrome. If it now runs stably, the GPU process was the culprit.
- Launch Chrome with a clean profile. In Terminal, run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome –user-data-dir=/tmp/chrome-test. If Chrome runs cleanly here, your main profile is corrupted. Back up bookmarks and passwords, then rename the folder at ~/Library/Application Support/Google/Chrome and let Chrome rebuild it.
- Disable all extensions. Navigate to chrome://extensions and toggle each one off. Restart Chrome and re-enable extensions one by one to identify the offender. Extensions related to ad-blocking, password management, and screen recording are the most common troublemakers after recent updates.
- Verify you’re running the correct architecture. On Apple silicon, download the ARM64 build directly from Google’s Chrome download page. In Finder, right-click Chrome, choose Get Info, and confirm the Kind shows “Application (Universal)” or “Apple Silicon.” Running the Intel build under Rosetta 2 is a leading cause of the recent crash reports.
- Reset Chrome to defaults. Go to Settings > Reset settings > Restore settings to their original defaults. This clears startup pages, pinned tabs, and site permissions without touching bookmarks or saved passwords.
- Clear the browser cache and cookies. Press Command+Shift+Delete, choose “All time,” and clear cached images, files, and cookies. A bloated cache combined with post-update schema changes can cause renderer crashes.
Additional Solutions
If the primary fixes didn’t resolve the crashes, these deeper interventions handle less common but confirmed cases.
Reinstall Chrome cleanly. Simply dragging Chrome to the Trash leaves behind support files that carry the corruption forward. Use a manual clean install: quit Chrome, delete /Applications/Google Chrome.app, then remove ~/Library/Application Support/Google/Chrome, ~/Library/Caches/Google/Chrome, and ~/Library/Preferences/com.google.Chrome.plist. Download a fresh installer and reinstall.
Check Console.app for crash signatures. Open Console from Applications > Utilities, filter by “Chrome,” and reproduce the crash. Look for GPU process termination messages, EXC_BAD_ACCESS errors, or references to specific system frameworks. These signatures often point directly to the conflicting component — commonly a third-party audio plugin, VPN kernel extension, or virtual camera driver.
Rebuild the Keychain permissions. Open Keychain Access, search for “Chrome Safe Storage,” and delete the entry. Chrome will regenerate it on next launch and re-request keychain access. This clears the login prompts and hangs that appear after major updates.
Disable experimental flags. Visit chrome://flags and click “Reset all.” Experimental features that worked in previous builds often break silently after security patches touch related code paths.
Check for macOS updates. Apple has been coordinating with Google on driver-level fixes. Head to System Settings > General > Software Update and install any pending macOS point releases, which often include GPU stack improvements Chrome depends on.
Test in a new macOS user account. Create a temporary user in System Settings > Users & Groups and log in. If Chrome runs perfectly there, the issue lives in your main account’s Library folder rather than in Chrome itself.
When to Contact Apple Support
Chrome is a third-party application, so Google is the first line of support for browser-specific bugs. However, contact Apple Support if:
- The crashes coincide with kernel panics or a full system freeze rather than just Chrome quitting.
- You see repeated GPU driver errors in Console that reference AppleGPU, IOSurface, or Metal frameworks.
- Other Chromium-based browsers exhibit identical symptoms, suggesting a macOS-level regression.
- Your Mac is under AppleCare and you suspect a hardware graphics fault.
Bring a sysdiagnose file (generate one by pressing Control+Option+Shift+Command+Period) to your Apple Support session — it gives technicians the crash logs they need immediately.
FAQ
Why did Chrome suddenly start crashing after being stable for months? A large batch of AI-assisted security patches shipped in rapid succession, and some fixes introduced regressions specific to macOS graphics and sandboxing.
Is downgrading Chrome safe? No. Older builds contain unpatched security vulnerabilities. Stay on the latest stable release and use the workarounds above instead.
Does this affect Safari or other browsers? Safari is unaffected. Other Chromium browsers such as Brave, Edge, and Arc can show similar symptoms because they share the same rendering engine.
Will resetting Chrome delete my bookmarks and passwords? No. Reset preserves bookmarks, history, and saved passwords. It clears startup settings, pinned tabs, site permissions, and disables extensions.
How do I stop Chrome from auto-updating? You can’t reliably block it on macOS, and you shouldn’t — the auto-updater is what delivers the security fixes. Focus on stabilizing the current version rather than freezing it.
Is this issue permanent? No. Google typically ships stability patches within one to two weeks of a regression being widely reported. Keeping Chrome updated is the long-term fix.
