From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 9A9DF2047F; Fri, 4 Aug 2017 19:10:23 +0000 (UTC) Date: Fri, 4 Aug 2017 19:10:23 +0000 From: Eric Wong To: Jeffrey Carl Faden Cc: unicorn-public@bogomips.org Subject: Re: initialize/fork crash in macOS 10.13 Message-ID: <20170804191023.GA28511@dcvr> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: Jeffrey Carl Faden wrote: > According to this post... > http://www.sealiesoftware.com/blog/archive/2017/6/5/Objective-C_and_fork_in_macOS_1013.html > > 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: This affects other Ruby programs which fork(). I suggest reporting to ruby-core @ https://bugs.ruby-lang.org/ and having somebody with macOS knowledge look at this(*). I don't even know how ObjC factors into this. > 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. Thanks for documenting this for other users, at least. I can't support macOS since I'm not allowed to know everything about it. (*) As a smug GNU/Linux user, I get to know EVERYTHING about how my system works from the kernel and up, for free! And when I do have a question I can't answer on my own; all I need to do is email the right people and lists. No NDAs or registration of any sort to deal with :>