Fix macOS Ansible worker crashes from ObjC fork safety#204
Merged
Conversation
On macOS with Python 3.14, the ObjC runtime aborts forked child processes when class initialisation (+[NSNumber initialize]) is in progress at fork time. This causes Ansible worker processes to crash with "A worker was found in a dead state" on every playbook run. Setting OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES in the Ansible subprocess environment prevents the crash.
l50
force-pushed
the
fix/macos-objc-fork-safety
branch
from
ff23f12 to
1a20847
Compare
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
2 participants
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.
Ansible workers crash immediately on macOS with Python 3.14, aborting every playbook at the "Gathering Facts" stage with
+[NSNumber initialize] may have been in progress in another thread when fork() was called.Fixed
OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YESis now injected automatically into the Ansible subprocess environment on Darwin, so users don't need to export it manually