Google Chrome that closes unexpectedly, sometimes right upon opening, sometimes after a few minutes of browsing, affects both Windows and Mac systems as well as certain Android tablets. The issue may stem from a corrupted user profile, a faulty extension, or a bug related to a specific version of the browser. The causes are not always the same, and guides that systematically suggest clearing the cache or reinstalling Chrome miss out on useful distinctions.
Chrome version bug and device-related closures
The majority of tutorials address Chrome closures as a generic problem. In reality, since 2025, specific bugs in certain versions of the browser have caused immediate closures on specific devices, particularly Android tablets from brands like Samsung, Xiaomi, or Lenovo. These crashes have no connection to installed extensions or a corrupted profile.
Recommended read : Taking Care of Yourself Daily: Tips and Tricks to Feel Beautiful and Good
Google typically fixes these bugs through silent updates deployed within a few days. Forcing an update from the Play Store or checking the release notes of Chrome is the most direct solution. Completely reinstalling the browser in this scenario is a waste of time on an unnecessary operation.
Several users report that a subsequent update of Chrome was enough to fix the problem without any further intervention. Before following a complex guide, it is better to identify if the bug is already documented on official forums or specialized sites, and look for solutions when Google Chrome closes by itself related to your exact version of the browser.
Recommended read : Legal tips to enjoy Spotify Premium for free: complete and updated guide
Corrupted Chrome profile on Windows: diagnosis before reinstallation
When Chrome crashes in a loop or only appears for a moment in the Task Manager on Windows, the user profile is often to blame. This profile stores preferences, cookies, history, and extension data. A corrupted file in this folder is enough to cause a systematic crash at launch.
Test with a blank profile
Before deleting everything, a simple check can isolate the cause. Renaming the Chrome profile folder (usually located in AppDataLocalGoogleChromeUser DataDefault on Windows) forces the browser to create a new one at the next launch. If Chrome works normally with this blank profile, the problem indeed lies with the original profile.
This operation avoids complete reinstallation and preserves the possibility of recovering certain files (bookmarks, passwords synced via the Google account). However, extensions and local settings will need to be reconfigured.
Launch Chrome without extensions
Launching Chrome with the flag –disable-extensions (via a modified shortcut on Windows) helps determine if an extension is causing the crash. If the browser remains stable, then the extensions should be reactivated one by one to identify the problematic one.
- Open the properties of the Chrome shortcut and add –disable-extensions after the path of the executable
- Launch Chrome via this shortcut and browse normally for several minutes
- If the browser remains stable, prioritize disabling recently installed or updated extensions
- Some extensions like built-in PDF viewers may automatically reinstall after deletion, indicating possible corruption
Accidental closure or software crash: two different problems
Content about “Chrome closing by itself” often mixes two distinct situations. The first concerns the accidental closure of tabs or the window due to a wrong click or an unintentional keyboard shortcut (Ctrl+W, Ctrl+Shift+Q on some configurations). The second corresponds to a true software crash, where Chrome stops functioning without user intervention.
The solutions differ radically. For accidental closures, preventive settings exist. For instance, PC Astuces documents methods to add a confirmation before closing Chrome, or to disable certain keyboard shortcuts. These tips are rarely mentioned in guides focused on “crash troubleshooting.”
For a true crash, the causes revolve around the system: conflict with an antivirus or overly restrictive firewall, outdated graphics driver, or lack of RAM. On a Windows machine with little RAM, opening about twenty tabs is enough to saturate resources and cause a sudden closure. The built-in Task Manager in Chrome (accessible via Shift+Esc) allows you to view the memory consumption of each tab and extension.
Chrome crashing on Mac: specificities to know
On macOS, the problem sometimes takes a different form. Users report that Chrome closes immediately after a system update or a browser update. The profile folder on Mac is located in /Library/Application Support/Google/Chrome/, and deleting it followed by a clean restart of the browser often resolves the issue.
The recommended procedure on Google forums is to uninstall Chrome using a thorough cleaning tool, delete the Google folder in Application Support, and then reinstall a fresh version. This approach remains relevant on Mac, as corrupted profiles after updates are more common than bugs related to a specific version of the browser.
- Delete the Chrome profile folder in /Library/Application Support/Google/Chrome/
- Clear residual files with a dedicated cleaning tool
- Reinstall Chrome from the official site and reconnect to the Google account to recover synchronization
When reinstallation is not enough: system leads
If Chrome continues to crash after a clean reinstallation and a new profile, the problem likely lies at the operating system level. An outdated or faulty graphics driver causes frequent crashes, especially on machines using hardware acceleration (enabled by default in Chrome). Disabling this option in Chrome’s advanced settings (chrome://settings > System) allows you to test this hypothesis.
A conflict with third-party security software can also block Chrome at startup. Some antivirus programs intercept the browser’s network connections and cause a sudden shutdown. Testing by temporarily disabling the antivirus helps confirm or rule out this possibility. The available data does not point to a specific software, as user feedback varies based on configurations.
On Windows, a system restore point created before the problem appeared remains one of the most reliable options to revert to a functional state without manually touching Chrome files. This precaution, rarely highlighted in troubleshooting guides, avoids hours of diagnosis on multiple overlapping causes.