LibSandbox: Report sandbox violations instead of killing the process#10240
Merged
gmta merged 1 commit intoJul 14, 2026
Merged
Conversation
Problem: Crash on macOS 15 due to the sandbox code. Cause: A helper symbolizes its own startup backtraces by reading its object files, which pulls in a code-signing check that macOS 15 denies. send-signal SIGSYS on the deny-default makes that process-killing fatal. Fix: Drop send-signal from the catch-all deny-default, so a violation is just denied+logged (the call returns EPERM), rather than fatally killing the process. That matches Chrome and Firefox: both make the deny-default non-fatal. The syscall-unix SIGKILL still hard-kills the real vectors.
sideshowbarker
force-pushed
the
macos-sandbox-report-violations
branch
from
June 27, 2026 02:06
0c67c12 to
078e778
Compare
gmta
approved these changes
Jul 14, 2026
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
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.
Problem: Crash on macOS 15 and 27 beta due to the sandbox code.
Cause: A helper symbolizes its own startup backtraces by reading its object files, which pulls in a code-signing check that macOS 15 (and 27?) denies.
send-signal SIGSYSon the deny-default makes that process-killing fatal.Fix: Drop
send-signalfrom the catch-all deny-default, so a violation is just denied+logged (the call returnsEPERM), rather than fatally killing the process. That matches Chrome and Firefox: both make the deny-default non-fatal. Thesyscall-unix SIGKILLstill hard-kills the real vectors.Hit this on my PR #9156 branch, which adds a GitHub-hosted macOS 15 (Sanitizer) CI job for AppKit+VoiceOver testing.
Also fixes #10379, which the issue reporter independently hit in a macOS 27 Golden Gate Developer Beta 2 environment. So perhaps this is somehow not actually related to the OS version. Or else I guess maybe the made some system change in the 27 beta that flipped it back to how it was in 15.