Chrome Crashes When Closing (Here’s the Simple Fixes That Work)

You’re about to close Google Chrome, but instead of a clean exit, you’re greeted by a frozen window, a cryptic error message, or an unexpected crash dialog. This frustrating pattern happens every single day, interrupting your workflow and leaving you wondering if something’s seriously broken.

Chrome crashes when closing primarily due to corrupted browser cache, misbehaving extensions, or outdated software. Background apps can also force Chrome to hang during shutdown. Clearing cache, disabling rogue extensions, updating the browser, and auditing background processes usually resolve exit crashes. For persistent issues, resetting settings or creating a fresh user profile eliminates profile corruption.

The good news? Most exit-related crashes stem from predictable culprits that live inside Chrome itself, cache fragments, extension conflicts, or profile data gone wrong. This guide walks you through systematic fixes that address every common cause of shutdown crashes.

Why Does Chrome Crash When You Close It?

Understanding the root causes helps you apply the right fix faster. Chrome exit crashes typically stem from three distinct problems: corrupted data, aggressive extensions, or version mismatches. Each creates a different failure signature, and identifying yours narrows the troubleshooting path.

Corrupted Browser Cache and Data

Chrome stores session data, cookies, cached images, and form inputs to speed up your next visit. When these files become corrupted, due to incomplete writes, sudden power loss, or disk errors, Chrome chokes during shutdown. The browser tries to serialize your session, hits a malformed entry, and throws an exception.

Session restore files (Current Session and Last Session) are frequent offenders. If Chrome crashes mid-session and fails to write a clean checkpoint, the next shutdown attempt can trigger the same error loop. Google’s official crash documentation confirms that profile corruption accounts for a significant portion of exit-related failures.

You can inspect crash reports at chrome://crashes to see timestamps and crash IDs. Windows Event Viewer also logs application faults under “Application” logs, often tagging them as chrome.exe exceptions with fault codes like 0xc0000005 (access violation). These codes point directly to memory corruption during cleanup routines.

“Chrome keeps crashing whenever I close it. Event Viewer shows ‘Application Error’ every single time.” via Google Chrome Help Community

If you’re running a VPN like NordVPN during heavy browsing, unstable tunnels can interrupt cache writes, amplifying the risk of corrupt session files. Stable network conditions help maintain data integrity during background saves.

Stay Private. Stay Secure.

Browse the internet with greater privacy and security with NordVPN. Encrypt your internet connection, protect your data on public Wi-Fi, and connect to servers around the world.

Get NordVPN

Problematic Extensions and Add-Ons

Extensions hook into Chrome’s lifecycle events, including shutdown. A poorly coded or outdated extension can block the close routine by holding file handles, performing long-running background tasks, or awaiting a callback that never arrives. Chrome waits, then times out, or just crashes.

Ad blockers, password managers, and productivity tools are common culprits. Extensions that sync data to cloud servers on exit can hang if the network is slow or the server unresponsive. Chrome Web Store policies require extensions to handle cleanup gracefully, but not all developers comply.

You can test for extension conflicts by launching Chrome in Incognito mode (Ctrl+Shift+N), which disables most extensions by default. If Incognito closes cleanly, an extension is your problem. Narrow it down by disabling extensions one at a time in chrome://extensions and testing after each.

Outdated Chrome Version

Google ships Chrome updates every few weeks, patching bugs, closing security holes, and fixing crash regressions. If you’re running an outdated build, you might be hitting a known exit-crash bug that’s already fixed upstream. Chrome’s auto-update mechanism usually handles this, but corporate policies, registry tweaks, or offline environments can block updates.

Check your version at chrome://settings/help. As of mid-2026, stable releases are in the 120–125 range. Anything below version 115 is dangerously outdated. Staying current protects you from both crashes and exploits.

Quick Fixes to Stop Chrome from Crashing on Exit

Start with these three rapid interventions. They resolve the majority of exit crashes in under five minutes and don’t require registry edits or third-party tools.

Clear Your Browsing Data and Cache

Corrupted cache is the single most common cause of shutdown crashes. Clearing it forces Chrome to rebuild session files from scratch. Here’s how:

1. Open Chrome and press Ctrl+Shift+Delete to launch the Clear Browsing Data dialog.
2. Select All time as the time range.
3. Check Cached images and files, Cookies and other site data, and Hosted app data.
4. Click Clear data.
5. Close Chrome completely (right-click the taskbar icon and choose Exit) and reopen.

This wipes session snapshots, forcing Chrome to start fresh. If you need to preserve passwords and autofill data, uncheck those boxes. Clearing cache is safe and non-destructive to bookmarks or extensions.

For deeper cleanup, navigate to %LocalAppData%\Google\Chrome\User Data\Default in File Explorer. Rename Current Session and Last Session files to .bak extensions. Chrome will generate new ones on the next launch.

Disable or Remove Problematic Extensions

Isolate the crashing extension with this workflow:

• Type chrome://extensions in the address bar.
• Toggle Developer mode in the top-right corner to see extension IDs.
• Disable all extensions by flipping each toggle to off.
• Close and reopen Chrome. If it exits cleanly, an extension is guilty.
• Re-enable extensions one by one, closing Chrome after each, until the crash returns.

Once you’ve identified the culprit, check the Chrome Web Store for an update or remove it entirely. Common offenders in 2026 include legacy ad blockers that haven’t migrated to Manifest V3 and older password managers that hook aggressively into form events.

Update Chrome to the Latest Version

Outdated builds carry known bugs. Updating is trivial:

1. Navigate to chrome://settings/help.
2. Chrome checks for updates automatically. If one is available, click Relaunch to install it.
3. After relaunch, test the exit behavior.

If auto-update is disabled by policy, download the latest Chrome installer directly from Google and run it to overwrite your existing installation. Enterprise users should consult IT before manual updates.

Advanced Solutions for Persistent Crash Issues

When quick fixes fail, deeper interventions target profile corruption, system conflicts, and malware. These steps require a bit more time but eliminate stubborn exit crashes.

Reset Chrome Settings to Default

Resetting restores factory defaults without deleting bookmarks or passwords. It disables extensions, clears startup pages, and resets search engines. This often breaks the crash loop caused by corrupted preferences.

1. Go to chrome://settings/reset.
2. Click Restore settings to their original defaults.
3. Confirm by clicking Reset settings.
4. Close and relaunch Chrome.

This operation leaves your profile intact but undoes customizations. If the crash persists, profile corruption is likely deeper than settings alone.

Create a New Chrome User Profile

Profile corruption can embed itself in SQLite databases, preference files, or extension storage. Creating a fresh profile bypasses all of it:

1. Close Chrome completely.
2. Navigate to %LocalAppData%\Google\Chrome\User Data.
3. Rename the Default folder to Default.old.
4. Relaunch Chrome. It creates a new Default folder with clean settings.
5. Test the exit behavior.

If Chrome now closes cleanly, your old profile was corrupt. Migrate bookmarks by copying Bookmarks and Bookmarks.bak from Default.old into the new Default folder. Extensions must be reinstalled manually.

“Creating a new profile fixed my crash-on-exit issue instantly. Turns out my old profile was hoarding 6 GB of junk.” via r/chrome

Check for Conflicting Software and Malware

Third-party software can inject DLLs into Chrome or block cleanup routines. Antivirus suites, firewall tools, and browser hijackers are frequent offenders. Use Malwarebytes or Microsoft Defender offline scan to hunt for malware.

Check Windows Event Viewer for clues:

• Press Win+X and select Event Viewer.
• Navigate to Windows Logs > Application.
• Filter for chrome.exe errors around the crash timestamps.
• Look for fault module names. If you see third-party DLLs, that software is interfering.

Disable startup programs via Task Manager (Ctrl+Shift+Esc > Startup tab). Tools like Driver Booster can help keep system drivers current, reducing the risk of driver-level conflicts that cascade into browser crashes. For hardware upgrades that reduce system strain, consider a high-performance SSD to speed up cache writes or a cooling pad for laptops if thermal throttling triggers instability.

Samsung SSD 9100 PRO 1TB, PCIe 5.0x4 M.2 2280, Up to 14,700MB/s

$339.99

$249.00

BUY NOW

Amazon.com

Comparison: Quick vs. Advanced Fixes

Read More:

• Chrome Freezes When Printing (Why and Simple Quick Steps)
• Chrome Disable Print Preview (How to Fix It for Instant Printing)
• Chrome Slow After Update (Common Causes and Expert Solutions)
• Chrome Slow on Windows 11 (Here’s the Proven Fixes That Work)
• Chrome Is Slow (Here’s Why and the Steps to Speed It Up)

Susan Miller

Susan is a professional writer. She has been a writer for eight years and has always been so fulfilled with her work! She desires to share helpful, reliable, and unbiased information and tips about tech and gadgets. She hopes to offer informative content that can answer users’ questions and help them fix their problems.