ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: shatrov@me.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:101797] [Ruby master Bug#17489] Ractor segfaults
Date: Mon, 28 Dec 2020 21:23:32 +0000 (UTC)	[thread overview]
Message-ID: <redmine.issue-17489.20201228212330.8653@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-17489.20201228212330.8653@ruby-lang.org

Issue #17489 has been reported by kirs (Kir Shatrov).

----------------------------------------
Bug #17489: Ractor segfaults
https://bugs.ruby-lang.org/issues/17489

* Author: kirs (Kir Shatrov)
* Status: Open
* Priority: Normal
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
I was able to boil it down to this script:

```ruby
require 'bundler/inline'

gemfile do
  source 'https://rubygems.org'
  gem "sinatra", "~> 2.1"
end

require 'sinatra'

class App < Sinatra::Base
  get '/' do
    200
  end
end

module Sinatra
  class Base
    class << self
      # patch it to avoid hitting other unsafe things
      def setup_default_middleware(builder)
        builder.use Rack::NullLogger
      end
    end
  end
end

workers = 2.times.map do
  Ractor.new { App.new }
end

Ractor.select(*workers)
```

Even though the code doesn't make a lot of sense and Sinatra has other stuff that's not compatible with Ractor, I would not expect user-level Ruby code to segfault.


I have attach the crash report and stderr output.

---Files--------------------------------
segfault.dump (44.8 KB)
ruby_2020-12-29-002108_Kirs-MacBook-Pro-2.crash (27.9 KB)


-- 
https://bugs.ruby-lang.org/

       reply	other threads:[~2020-12-28 21:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-28 21:23 shatrov [this message]
2021-01-05  1:34 ` [ruby-core:101919] [Ruby master Bug#17489] Ractor segfaults ko1
2021-01-05 21:25 ` [ruby-core:101940] " yura.des
2022-03-25 11:29 ` [ruby-core:108066] " wanabe (_ wanabe)
2022-03-26  9:50 ` [ruby-core:108083] " kirs (Kir Shatrov)
2022-03-26 20:36 ` [ruby-core:108086] " wanabe (_ wanabe)

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-17489.20201228212330.8653@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).