Skip to content

Fix macOS Ansible worker crashes from ObjC fork safety #204

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
l50 merged 2 commits into from
May 15, 2026
+11 −0
Merged

Fix macOS Ansible worker crashes from ObjC fork safety #204

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1a20847
fix: disable ObjC fork safety check on macOS for Ansible workers
mkultraWasHere May 15, 2026
c8db75e
Merge branch 'main' into fix/macos-objc-fork-safety
l50 May 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions cli/internal/ansible/runner.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ import (
"os"
"os/exec"
"path/filepath"
"runtime"
"strings"
"sync/atomic"
"syscall"
Expand Down Expand Up @@ -229,6 +230,16 @@ func buildArgs(opts RunOptions, cfg *config.Config) []string {
func buildEnv(opts RunOptions, cfg *config.Config) ([]string, error) {
env := os.Environ()

// On macOS, the ObjC runtime aborts forked child processes when class
// initialisation is in progress at fork time. Ansible forks workers
// heavily, which triggers:
// "+[NSNumber initialize] may have been in progress in another thread
// when fork() was called … Crashing instead."
// Setting this variable tells the runtime to skip the check.
if runtime.GOOS == "darwin" {
env = append(env, "OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES")
}

ansibleEnv, err := cfg.AnsibleEnv()
if err != nil {
return nil, fmt.Errorf("ansible env: %w", err)
Expand Down
Loading