From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: poffice@blade.nagaokaut.ac.jp Delivered-To: poffice@blade.nagaokaut.ac.jp Received: from kankan.nagaokaut.ac.jp (kankan.nagaokaut.ac.jp [133.44.2.24]) by blade.nagaokaut.ac.jp (Postfix) with ESMTP id D846C19C003A for ; Tue, 3 Nov 2015 12:04:41 +0900 (JST) Received: from voscc.nagaokaut.ac.jp (voscc.nagaokaut.ac.jp [133.44.1.100]) by kankan.nagaokaut.ac.jp (Postfix) with ESMTP id 32840B5D94C for ; Tue, 3 Nov 2015 12:33:21 +0900 (JST) Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by voscc.nagaokaut.ac.jp (Postfix) with ESMTP id 36FF295241E for ; Tue, 3 Nov 2015 12:33:20 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 69C2012050B; Tue, 3 Nov 2015 12:33:19 +0900 (JST) X-Original-To: ruby-core@ruby-lang.org Delivered-To: ruby-core@ruby-lang.org Received: from dcvr.yhbt.net (dcvr.yhbt.net [64.71.152.64]) by neon.ruby-lang.org (Postfix) with ESMTP id 082191204B8 for ; Tue, 3 Nov 2015 12:33:15 +0900 (JST) Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id F3AE31F82C; Tue, 3 Nov 2015 03:33:13 +0000 (UTC) Date: Tue, 3 Nov 2015 03:33:13 +0000 From: Eric Wong To: Ruby developers Message-ID: <20151103033313.GA2528@dcvr.yhbt.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-ML-Name: ruby-core X-Mail-Count: 71305 Subject: [ruby-core:71305] Re: [Ruby trunk - Bug #11384] multi-threaded autoload sometimes fails 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: , Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" shugo@ruby-lang.org wrote: > It's still running beyond 49,000 times on my notebook, which sleeps at night. > I'll inform you if any error occurs. Actually, I've managed to reproduce around 47,000 times. So my patch (r52332) seems to help make the problem less obvious, but yeah, there's still a bug somewhere...