unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
* initialize/fork crash in macOS 10.13
@ 2017-08-04 16:40 Jeffrey Carl Faden
  2017-08-04 19:10 ` Eric Wong
  0 siblings, 1 reply; 3+ messages in thread
From: Jeffrey Carl Faden @ 2017-08-04 16:40 UTC (permalink / raw)
  To: unicorn-public

According to this post...

The rules around initialize and fork() have changed in macOS 10.13, which is coming out in a month or so. I tried using Unicorn today to run a unicorn_rails instance, and got this as part of my traceback:

objc[95737]: +[__NSPlaceholderDictionary 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.
E, [2017-08-04T08:35:28.148339 #95531] ERROR -- : reaped #<Process::Status: pid 95736 SIGABRT (signal 6)> worker=1

I'm not sure if this is something downstream, but I thought I'd bring it to your attention. My temporary solution is to preface my commands with OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES.


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-10-16 19:25 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-08-04 16:40 initialize/fork crash in macOS 10.13 Jeffrey Carl Faden
2017-08-04 19:10 ` Eric Wong
2017-10-16 19:25   ` Eric Wong

Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).