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 DE98519C026F for ; Thu, 19 Nov 2015 15:24:44 +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 062B3B5D87E for ; Thu, 19 Nov 2015 15:55:29 +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 4F7D118CC7F2 for ; Thu, 19 Nov 2015 15:55:29 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id F3DF9120477; Thu, 19 Nov 2015 15:55:28 +0900 (JST) X-Original-To: ruby-core@ruby-lang.org Delivered-To: ruby-core@ruby-lang.org Received: from o2.heroku.sendgrid.net (o2.heroku.sendgrid.net [67.228.50.55]) by neon.ruby-lang.org (Postfix) with ESMTPS id 126AF120468 for ; Thu, 19 Nov 2015 15:55:22 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.me; h=from:to:references:subject:mime-version:content-type:content-transfer-encoding:list-id; s=smtpapi; bh=xgr+895URDtYEaotDaTYD4e0Bzg=; b=nVxGTIRrQaDPkXNusP ojO5/EFdVGd8s1vz26bYnw58ZSAgHFMKU9I4TBtmlMcXVMGcxiije0FvKT3MU+wr RDus62tWXMDfJrdgnMip+zk+rZnIw8tufUud8K/QVeu1sSC/N5LipJVqdeLPp1FE Pf9TIpBO84jBC9OuRO2mQT7wY= Received: by filter0471p1mdw1.sendgrid.net with SMTP id filter0471p1mdw1.31192.564D725645 2015-11-19 06:55:18.777180268 +0000 UTC Received: from herokuapp.com (ec2-54-224-166-174.compute-1.amazonaws.com [54.224.166.174]) by ismtpd0006p1iad1.sendgrid.net (SG) with ESMTP id StY8v22MTAapKbjpV0u3yA for ; Thu, 19 Nov 2015 06:55:18.776 +0000 (UTC) Date: Thu, 19 Nov 2015 06:55:18 +0000 From: ko1@atdot.net To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Redmine-MailingListIntegration-Message-Ids: 46234 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 11692 X-Redmine-Issue-Author: gazay X-Redmine-Issue-Assignee: ko1 X-Redmine-Sender: ko1 X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-SG-EID: ync6xU2WACa70kv/Ymy4QrNMhiuLXJG8OTL2vJD1yS4ZFC8VXeHeGtQH3Q96MUAAyO5fFXucAP2qDy vOTxvmjJHP01PGyiVljA7wICyLH+zlDyCzpvs1bRpQJJj3kMlMoCk/ta/JVNu5QTTcQZSUFbWZ3Uny HZqGjqeaIf0xwaibhQv8gBZ+Ri3uwgLUGZaa X-ML-Name: ruby-core X-Mail-Count: 71571 Subject: [ruby-core:71571] [Ruby trunk - Bug #11692] [PATCH] Re-enable GC if stack overflow was caught from signal handler 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" Issue #11692 has been updated by Koichi Sasada. Assignee set to Koichi Sasada Thank you for your great survey! ---------------------------------------- Bug #11692: [PATCH] Re-enable GC if stack overflow was caught from signal handler https://bugs.ruby-lang.org/issues/11692#change-54953 * Author: Alex Gaziev * Status: Closed * Priority: Normal * Assignee: Koichi Sasada * ruby -v: * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN ---------------------------------------- We got ruby application running on our production server and noticed that it regularly crashes with out of memory errors. After months of investigation, I narrowed the case to the examples (1/2). After digging ruby sources and running test code, I found out that GC stopped working after recovering from native stack overflow error. Probably the relevant code appeared in 2.2 https://github.com/ruby/ruby/commit/0c391a55d3ed4637e17462d9b9b8aa21e64e2340 where ruby_disable_gc_stress became ruby_disable_gc. Patches for trunk and 2.2 branches below. ---Files-------------------------------- example1.rb (311 Bytes) example2.rb (333 Bytes) re-enable-gc-after-stackoverflow-trunk.patch (985 Bytes) re-enable-gc-after-stackoverflow-ruby-2-2.patch (985 Bytes) gc_threads_issue.rb (1.53 KB) -- https://bugs.ruby-lang.org/