From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS4713 221.184.0.0/13 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id 84E0B1F87F for ; Mon, 19 Nov 2018 00:22:56 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id AD4D1120D2A; Mon, 19 Nov 2018 09:22:54 +0900 (JST) Received: from dcvr.yhbt.net (dcvr.yhbt.net [64.71.152.64]) by neon.ruby-lang.org (Postfix) with ESMTPS id 524591209A1 for ; Mon, 19 Nov 2018 09:22:51 +0900 (JST) Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 52ADE1F87F; Mon, 19 Nov 2018 00:22:49 +0000 (UTC) Date: Mon, 19 Nov 2018 00:22:49 +0000 From: Eric Wong To: ruby-core@ruby-lang.org Message-ID: <20181119002248.3zp4kib7sbl2dpyy@dcvr> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-ML-Name: ruby-core X-Mail-Count: 89859 Subject: [ruby-core:89859] Re: [Ruby trunk Bug#15316] rb_postponed_job_register not thread-safe X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" takashikkbn@gmail.com wrote: > Well, I seem to have introduced at least two deadlocks by > that. I already fixed the first one, and I'm going to fix the > second one > http://ci.rvm.jp/results/trunk-mjit@silicon-docker/1467162. > > I'll take a deeper look when I come home today, but do you > know who wakes up rb_sigwait_sleep and/or how the hang there > could happen? Any signal should wake it up... If you can't solve it, can you wait until after the 11/22 developers meeting? It's a small chance, but I really want to get Thread::Light (auto-fiber) ready and into 2.6 (at least for Linux/FreeBSD), and I barely have time for Ruby as it is. It's not looking like I'll be able to afford to hack on Ruby next year :<