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: AS4713 221.184.0.0/13 X-Spam-Status: No, score=-3.4 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.0 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id 9F5671F424 for ; Mon, 23 Apr 2018 13:39:55 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 76B46120914; Mon, 23 Apr 2018 22:39:53 +0900 (JST) Received: from dcvr.yhbt.net (dcvr.yhbt.net [64.71.152.64]) by neon.ruby-lang.org (Postfix) with ESMTPS id 084B212090B for ; Mon, 23 Apr 2018 22:39:49 +0900 (JST) Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 46FA31F424; Mon, 23 Apr 2018 13:39:46 +0000 (UTC) Date: Mon, 23 Apr 2018 13:39:46 +0000 From: Eric Wong To: ruby-core@ruby-lang.org Message-ID: <20180423133946.GA6019@dcvr> MIME-Version: 1.0 Content-Disposition: inline X-ML-Name: ruby-core X-Mail-Count: 86655 Subject: [ruby-core:86655] cross-thread IO#close semantics 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" Related to the discussion on [Bug #14681] I found an old Ruby 1.8 installation, and the following code exits after 100ms with: [IOError, "stream closed"] 1.9 and later hangs forever: r, w = IO.pipe th = Thread.new do begin IO.select([r]) rescue => e warn [ e.class, e.message ].inspect end end sleep 0.1 r.close th.join Of course I know why: it's not implemented in 1.9+; rb_thread_io_blocking_region only cares for operations on the single FD case, multiplexing functions like select aren't supported. I could implement it, but it has overhead and maybe nobody cares for this feature. IO.select is an inefficient API anyways This also pertains to [Feature #13618] for auto-fiber/green thread support or whatever it will be called. If I replace IO.select with single FD operation which hits rb_thread_io_blocking_region in 1.9+ such as "r.read", then Ruby behaves consistently in 1.8/1.9/2.x