A Chrome process that ends without a visible error message rarely points to a single cause. The browser manages each tab and extension in a separate process, and sudden closure often results from a conflict between these processes and the system environment. Understanding the internal mechanisms allows for faster isolation of the failure than following a list of generic solutions.
Manifest V3 and incompatible extensions: the cause that Chrome does not report
Google has accelerated the phasing out of Manifest V2 for Chrome extensions. Since the gradual rollout announced in May 2024, extensions that have not migrated to MV3 may be silently disabled or cause crashes of the main process.
Related reading : How to Eliminate Swing Creaking: Tips and Effective Solutions
The typical symptom: Chrome closes a few seconds after loading a tab that requires an ad blocker extension, a password manager, or a capture tool. The extension attempts to execute with removed APIs, the child process fails, and the browser closes the parent window.
We recommend opening chrome://extensions and checking if a banner indicates disabled extensions for non-compliance. If in doubt, disable all extensions, then reactivate them one by one, restarting Chrome between each activation. The faulty extension will reveal itself immediately. If you are looking for solutions if Chrome closes by itself, this elimination diagnosis remains the most reliable method before any reinstallation.
Related reading : Discover the best delicious recipes to delight the whole family
Hardware acceleration and GPU drivers on Windows: isolating the graphics conflict
Disabling hardware acceleration is an old piece of advice, but the technical reason has evolved. Chrome now uses ANGLE (Almost Native Graphics Layer Engine) to translate WebGL calls and accelerated 2D rendering. When the installed GPU driver does not properly support ANGLE calls, Chrome’s GPU process crashes and leads to the closure of all windows.
On Windows, this conflict particularly affects integrated Intel graphics cards with outdated drivers. Chrome attempts accelerated rendering, the GPU process fails, and the browser interprets the failure as fatal.
Diagnosis via chrome://gpu
Access chrome://gpu in the address bar. The “Graphics Feature Status” section lists each function (WebGL, Rasterization, Video Decode) with a status: Hardware accelerated, Software only, or Disabled. If multiple lines display “Disabled” or “Software only,” the GPU driver is problematic.
- Update the GPU driver directly from the manufacturer’s website (Intel, NVIDIA, AMD), not from Windows Update which often distributes generic versions
- If the update changes nothing, force the disablement in chrome://settings > System > uncheck “Use hardware acceleration”
- Restart Chrome and test stability over several sessions before concluding
This is not a temporary workaround. Some hardware configurations remain incompatible with Chrome’s graphics pipeline, and permanent disablement only affects the rendering of complex CSS animations and WebGL.
Corrupted user profile: the User Data folder as a point of failure
Chrome stores the entire session (cookies, history, form data, extension settings) in a User Data folder. A corruption of the Local State file or the Default folder causes immediate closures upon launch, sometimes even before the interface is displayed.
On Windows, this folder is located in %LOCALAPPDATA%GoogleChromeUser Data. Corruption occurs after a sudden power cut (blue screen, forced shutdown) or when an antivirus locks a file while Chrome attempts to write to it.
Rename rather than delete
Rename the “Default” folder to “Default.bak” before restarting Chrome. The browser will recreate a blank profile. If Chrome works normally with this new profile, the corruption is confirmed.
You can then recover specific data from the saved folder: bookmarks are found in the “Bookmarks” file (JSON format, directly copyable). Passwords and history are encrypted and linked to the profile, so they cannot be transferred manually. For this data, synchronization via a Google account remains the only reliable recovery mechanism.
Safety Check and closures related to Chrome’s built-in protections
Chrome has strengthened its protections against unwanted software through the Safety Check mechanism, updated in 2024-2025. This system analyzes installed extensions, recent downloads, and browser settings in the background.
When Safety Check detects a third-party component classified as potentially dangerous, it may neutralize the associated extension or process. In some cases, this neutralization triggers a cascade of errors that closes Chrome without explicit notification.
- Open chrome://settings/safetyCheck to check if any alerts are pending
- Check chrome://crashes to identify recent crash reports, each accompanied by an ID and timestamp
- If a recurring crash mentions “EXCEPTION_ACCESS_VIOLATION,” it points to a memory conflict with third-party software (antivirus, VPN, monitoring tool)
Antiviruses that inject DLLs into the Chrome process are a frequent source of this type of conflict. We regularly observe this issue with security solutions that intercept HTTPS traffic via a local proxy.
Clean reinstallation of Chrome: the procedure that actually works
Uninstalling Chrome via the Windows control panel does not remove the User Data folder. Reinstalling over a corrupted profile reproduces the same problem.
The effective procedure consists of uninstalling Chrome, then manually deleting the %LOCALAPPDATA%GoogleChrome folder before reinstalling. This deletion eliminates the profile, cache, extension data, and local configuration files.
Synchronize your data via your Google account before this operation. Bookmarks, saved passwords, history, and settings will be automatically restored upon first login to the new profile. Without prior synchronization, this data is permanently lost.
The issue of Chrome closing without explanation almost always relates to an incompatible MV3 extension, a GPU conflict, or a corrupted profile. Identifying the category of the problem before taking action avoids reformatting or reinstalling Windows for a simple Local State file to rename.