unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Jeffrey Carl Faden <jeffreyatw@gmail.com>
To: unicorn-public@bogomips.org
Subject: initialize/fork crash in macOS 10.13
Date: Fri, 4 Aug 2017 09:40:16 -0700	[thread overview]
Message-ID: <F28C7A88-7048-47A4-9B31-1D4AA128604D@gmail.com> (raw)

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.


             reply	other threads:[~2017-08-04 16:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04 16:40 Jeffrey Carl Faden [this message]
2017-08-04 19:10 ` initialize/fork crash in macOS 10.13 Eric Wong
2017-10-16 19:25   ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F28C7A88-7048-47A4-9B31-1D4AA128604D@gmail.com \
    --to=jeffreyatw@gmail.com \
    --cc=unicorn-public@bogomips.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).