Skip to content
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.

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

macOS users, please notice: #1

Open
niryarden opened this issue Nov 26, 2019 · 0 comments
Open

macOS users, please notice: #1

niryarden opened this issue Nov 26, 2019 · 0 comments

Comments

@niryarden
Copy link
Contributor

niryarden commented Nov 26, 2019

macOS users, please notice:

Bug

If you'll try running log scanner manually with python, and not with docker, it'll probably crash with these messages:

objc[35301]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called.
objc[35301]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.

Explanation

That issue is caused due to some new security changes made in High Sierra macOS that are breaking a lot of Python program that use forking. For further explanation, please check out this link. In general, a new mechanism aimed to detect the usage of forking (which the log scanner most certainly does).

Solution

You can either run the scanner with docker, as described, or set a temporary environment variable which will disable that fork safety mechanism:

export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES

enjoy :)

@niryarden niryarden reopened this Nov 26, 2019
@niryarden niryarden pinned this issue Nov 26, 2019
@niryarden niryarden reopened this Nov 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant