Google Chrome closing unexpectedly, without error messages, sometimes right upon opening: this issue affects both recent machines running Windows 11 and Linux systems using Snap or Flatpak builds. The causes range from simple extension conflicts to deep incompatibilities between the browser and a security component of the system. Identifying the responsible layer can help avoid unnecessary reinstallation of Chrome.
Conflict between Chrome’s sandbox and system security modules
The least visible, yet most frequent issue on recent machines, concerns the coexistence between Chrome’s integrated sandbox and the protection layers of the operating system. Two mechanisms regularly collide.
Read also : Mastering the Forefoot Running Technique: Tips and Mistakes to Avoid
On Windows 10 and Windows 11, the enhanced activation of “Core Isolation” and its “Memory Integrity” option can cause repeated closures of Chrome. The browser closes without displaying any message when the machine uses outdated or unsigned drivers.
The only lasting fix involves updating the problematic driver, or, as a last resort, temporarily disabling memory integrity in the Windows security settings.
Related reading : How to Choose the Right Size on Zalando: Tips and Practical Advice
In a professional environment, the problem takes another form. Since 2023, several antivirus and EDR solution providers (Bitdefender, Kaspersky, CrowdStrike, among others) have documented cases where their web protection modules directly conflict with Chrome’s sandbox.
The result: immediate closure upon opening or loading certain sites. Fixes have come from updates to signatures or the security agent, not from Chrome itself. Knowing what to do if Chrome closes by itself thus requires checking the status of these security layers before touching the browser.
To test this hypothesis, the quickest way is to launch Chrome with the –no-sandbox flag from a command prompt. If Chrome operates normally in this mode, the conflict is confirmed. This flag should never remain active on a daily basis: it disables the browser’s security protection.
Corrupted extensions and user profile: methodical diagnosis
Extensions are the most documented cause of unexpected closures, but the diagnostic method is as important as the observation. Disabling all extensions at once, then reactivating them one by one, remains the only reliable way to isolate the faulty extension.
Opening Chrome in incognito mode (Ctrl+Shift+N on Windows, Cmd+Shift+N on macOS) allows starting without any active extensions. If Chrome remains stable in incognito mode but crashes in normal mode, an extension or the user profile is to blame.
- Access chrome://extensions/ and disable all extensions, then reactivate them one by one while testing stability after each reactivation
- Check if the user profile is corrupted by creating a new profile via chrome://settings/ then “Add person”: if the new profile works, the old profile contains corrupted data
- Rename (do not delete) the default profile folder (Default) in the Chrome data directory to force the creation of a new profile
A profile accumulating several years of browsing data, bookmarks, and settings can sometimes contain malformed JSON preference files. Corruption does not always manifest at the same time: some users find that Chrome only closes when clicking on the bookmarks bar, a behavior reported on several support forums.
Chrome closing on Linux: the Snap and Flatpak pitfalls
Linux users face a category of problems specific to packaged builds. The Snap and Flatpak versions of Chrome and Chromium have experienced regressions in 2023 and 2024 where the browser closed without warning after a few seconds of use, or refused to start after a system update.
These closures most often stem from missing permissions in the sandboxing container specific to Snap or Flatpak. Denied access to the file system, GPU, or display server (Wayland or X11) is enough to cause a silent shutdown. Consulting the logs with the command snap logs chromium or flatpak run --verbose can help identify the exact error.
Switching to the native .deb package (on Debian/Ubuntu distributions) or the official RPM remains the most reliable solution when Snap or Flatpak container regressions persist.
Hardware acceleration and outdated graphics drivers
Chrome uses the GPU for rendering pages, video playback, and certain CSS animations. An outdated or faulty graphics driver can cause a complete browser crash, sometimes accompanied by a fleeting black screen before the window closes.
Disabling hardware acceleration is the quickest test:
- Open chrome://settings/, section “System”, disable “Use hardware acceleration when available”, then relaunch the browser
- Check the GPU status via chrome://gpu/ to identify disabled features or those flagged as problematic
- Update the graphics driver from the manufacturer’s website (NVIDIA, AMD, Intel) rather than through Windows Update, which sometimes distributes older versions
If Chrome stops closing after disabling hardware acceleration, the graphics driver is the direct cause of the crash. Permanently disabling hardware acceleration reduces browsing smoothness and video playback quality: it is better to invest the necessary time to update the driver.
Field reports vary on the effectiveness of a complete reset of Chrome (chrome://settings/reset) in this specific case. It removes extensions, cookies, and custom settings, but does not fix an underlying driver issue. Resetting remains a last resort, to be considered only after eliminating the system and hardware causes described above.