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 F3FEE196000B for ; Sun, 21 Jun 2015 19:37:41 +0900 (JST) Received: from funfun.nagaokaut.ac.jp (funfun.nagaokaut.ac.jp [133.44.2.201]) by kankan.nagaokaut.ac.jp (Postfix) with ESMTP id A4F44B5D93C for ; Sun, 21 Jun 2015 20:01:04 +0900 (JST) Received: from funfun.nagaokaut.ac.jp (localhost.nagaokaut.ac.jp [127.0.0.1]) by funfun.nagaokaut.ac.jp (Postfix) with ESMTP id 047AF97A827 for ; Sun, 21 Jun 2015 20:01:07 +0900 (JST) X-Virus-Scanned: amavisd-new at nagaokaut.ac.jp Authentication-Results: funfun.nagaokaut.ac.jp (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=sendgrid.me Received: from funfun.nagaokaut.ac.jp ([127.0.0.1]) by funfun.nagaokaut.ac.jp (funfun.nagaokaut.ac.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jFdt-4XGkKbN for ; Sun, 21 Jun 2015 20:01:06 +0900 (JST) Received: from voscc.nagaokaut.ac.jp (voscc.nagaokaut.ac.jp [133.44.1.100]) by funfun.nagaokaut.ac.jp (Postfix) with ESMTP id 8621E97A820 for ; Sun, 21 Jun 2015 20:01:06 +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 0126595243A for ; Sun, 21 Jun 2015 20:01:03 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 56A6612047D; Sun, 21 Jun 2015 20:01:02 +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 B999A12046D for ; Sun, 21 Jun 2015 20:00:55 +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=Ltrcji/9MFrdGaG+UGgAflgOJHQ=; b=wA3Z7nmmQK5Emsma8C bCt3r6a0UbiuK7S4PIxvduxmx+i78tE2wxVqsaCWa78/YLOgR0KWVu3NQ7KUY4Gm oHr+fHvA9p1zgObr6lz7jRZ/HgnSLRaHGZl90YBLEBmnRZAmw/EJLPmn5MaRhejy tCc2DyybZ9og1EwBRJuWS/H34= Received: by filter0650p1mdw1.sendgrid.net with SMTP id filter0650p1mdw1.10569.558699632 2015-06-21 11:00:51.427578374 +0000 UTC Received: from herokuapp.com (ec2-54-166-46-92.compute-1.amazonaws.com [54.166.46.92]) by ismtpd-001 (SG) with ESMTP id 14e15c72bdc.21c9.b8860 Sun, 21 Jun 2015 11:00:51 +0000 (UTC) Date: Sun, 21 Jun 2015 11:00:51 +0000 From: michael@netronix.be To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Redmine-MailingListIntegration-Message-Ids: 44256 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 10968 X-Redmine-Issue-Author: geoffroy X-Redmine-Issue-Assignee: ko1 X-Redmine-Sender: netronix 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/Ymy4QrNMhiuLXJG8OTL2vJD1yS4A6KXQ35PHQg5UZ1KLbUnQBddWW+JRIy2O6c TQGN6IpKwcJXYYkEsBTalZJwc0BtKPd8cUqHOrtwPciflsrbrUcrlPrtDxXacySHFJCTBMgqRYEjYN 9XhwLguY1Ub7d/r5QvUAMsMW9CgSmpVE/ahW X-ML-Name: ruby-core X-Mail-Count: 69696 Subject: [ruby-core:69696] [Ruby trunk - Bug #10968] [BUG] object allocation during garbage collection phase in /opt/rubies/ruby-2.2.1/lib/ruby/2.2.0/openssl/ssl.rb:177 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 #10968 has been updated by Micha=C3=ABl Rigart. File stacktrace.txt added Zachary Scott wrote: > Do you know how to reproduce it? >=20 > Rails+Ruby 2.2 isn't enough for me to make a crash. I was able to reduce the frequency by updating some gems. Now, instead of h= appening in different cases, it only seems to happen on routines that fetch= data from an external API's ( yammer and Diigo ).=20 Going to have a look in more detail if I find a common denominator. ---------------------------------------- Bug #10968: [BUG] object allocation during garbage collection phase in /opt= /rubies/ruby-2.2.1/lib/ruby/2.2.0/openssl/ssl.rb:177 https://bugs.ruby-lang.org/issues/10968#change-53072 * Author: Geoffroy Montel * Status: Feedback * Priority: Normal * Assignee: Koichi Sasada * ruby -v: 2.2.1p85 (2015-02-26 revision 49769) [x86_64-linux] * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN ---------------------------------------- Hello I'm running a Rails 4.2 app in production with chruby 0.3.9 and Ruby 2.2.1p= 85 on Ubuntu 14.04TLS.=20 I have several unicorn and workers processes. I got this crash on my cron jobs several times Thu Mar 12 08:30:01 CET 2015 /usr/local/share/chruby/chruby-cron-wrapper.sh= instatube:clean_up_assets - started by deployer on /bin/bash /opt/rubies/ruby-2.2.1/lib/ruby/2.2.0/openssl/ssl.rb:177: [BUG] object allo= cation during garbage collection phase ruby 2.2.1p85 (2015-02-26 revision 49769) [x86_64-linux] -- Control frame information ----------------------------------------------- c:0028 p:---- s:0134 e:000133 CFUNC :peer_cert c:0027 p:0016 s:0131 e:000129 METHOD /opt/rubies/ruby-2.2.1/lib/ruby/2.2.0/= openssl/ssl.rb:177 c:0026 p:0584 s:0126 e:000125 METHOD /opt/rubies/ruby-2.2.1/lib/ruby/2.2.0/= net/http.rb:925 Full stack trace attached. Many thanks in advance for your help, best regards Geoffroy ---Files-------------------------------- object allocation bug ssl.txt (203 KB) stacktrace.txt (215 KB) stacktrace.txt (201 KB) --=20 https://bugs.ruby-lang.org/