Skip single-process flag on macOS to prevent Chromium crashes - #45
Open
flgusto wants to merge 1 commit into
Open
Skip single-process flag on macOS to prevent Chromium crashes#45flgusto wants to merge 1 commit into
flgusto wants to merge 1 commit into
Conversation
The --single-process Chrome flag, required for screenshots in gVisor/container environments, causes Chromium to crash on macOS when navigating to complex sites. Only set the flag on non-Darwin platforms. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Author
|
Related to: #9 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
--single-processChrome flag, required for screenshots in gVisor/container environments, causes Chromium to crash on macOS when navigating to complex sites (e.g. pages with Keycloak SSO, media permission checks). Simple sites and local dev servers work fine.In single-process mode, all Chromium subsystems share one process. When any subsystem hits a fatal condition — such as a macOS TCC permission check (e.g. microphone) that can't display a prompt — it takes down the entire browser. In multi-process mode these crashes are isolated and recoverable.
Evidence from crash reports:
EXC_BREAKPOINT/SIGTRAPon a thread queued forcom.apple.tcc.preflight.kTCCServiceMicrophoneSIGABRTinCFBundleGetInfoDictionaryonCrBrowserMainThis change only skips the flag on Darwin. Linux and Windows behavior is unchanged.