From: pikachuexe@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:91626] [Ruby trunk Bug#15623] Ruby 2.6.1 Segmentation Fault in on Phusion Passenger server boot in dev
Date: Wed, 27 Feb 2019 03:03:19 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-15623.20190227030317.16b529ce48d114c1@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15623.20190227030317@ruby-lang.org
Issue #15623 has been reported by PikachuEXE (Pikachu Leung).
----------------------------------------
Bug #15623: Ruby 2.6.1 Segmentation Fault in on Phusion Passenger server boot in dev
https://bugs.ruby-lang.org/issues/15623
* Author: PikachuEXE (Pikachu Leung)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.6.1p33 (2019-01-30 revision 66950) [x86_64-darwin18]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
Ruby is install via RVM
Passenger is install via gem install/bundle install
It's not always crashing the same thread
Happens in 2.6.0 too
But not in 2.5.x
---Files--------------------------------
ruby_2019-02-27-104653_PikachuEXEs-MBP-2018.crash (88.5 KB)
ruby_2019-02-27-104653-1_PikachuEXEs-MBP-2018.crash (94.7 KB)
ruby_2019-02-27-104653-2_PikachuEXEs-MBP-2018.crash (88.6 KB)
ruby_2019-02-27-104719_PikachuEXEs-MBP-2018.crash (64.7 KB)
ruby_2019-02-27-104719-1_PikachuEXEs-MBP-2018.crash (65.9 KB)
ruby_2019-02-27-104719-2_PikachuEXEs-MBP-2018.crash (66.1 KB)
ruby_2019-02-27-105022_PikachuEXEs-MBP-2018.crash (53.3 KB)
--
https://bugs.ruby-lang.org/
next parent reply other threads:[~2019-02-27 3:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-15623.20190227030317@ruby-lang.org>
2019-02-27 3:03 ` pikachuexe [this message]
2019-02-27 3:08 ` [ruby-core:91627] [Ruby trunk Bug#15623] Ruby 2.6.1 Segmentation Fault in on Phusion Passenger server boot in dev pikachuexe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.issue-15623.20190227030317.16b529ce48d114c1@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).