From: anthony@noided.media
To: ruby-core@ruby-lang.org
Subject: [ruby-core:100181] [Ruby master Bug#17196] Segmentation Fault with Socket#close in Ractors
Date: Sat, 26 Sep 2020 21:18:59 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-17196.20200926211858.44579@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-17196.20200926211858.44579@ruby-lang.org
Issue #17196 has been reported by asuper (Anthony Super).
----------------------------------------
Bug #17196: Segmentation Fault with Socket#close in Ractors
https://bugs.ruby-lang.org/issues/17196
* Author: asuper (Anthony Super)
* Status: Open
* Priority: Normal
* ruby -v: ruby 3.0.0preview1 (2020-09-25 master 0096d2b895) [x86_64-linux]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
While messing around with 3.0.0-preview1, I thought it would be fun to write a really, really simple webserver that used Ractor creation instead of forking or spawning threads. I was right, it was fun! Unfortunately it also caused a segfault. The segfault appears to be on socket closure when a *lot* of ractors are running at once.
The attached tarball includes the code you need to make it happen. Run `bin/server` in one terminal/screen session/tmux window/whatever, and `./bug_bench.sh` with the other. You'll need to have the apache benchmark utility installed.
---Files--------------------------------
reproduce-my-segfault.tar.gz (10 KB)
error_log.txt (38.6 KB)
--
https://bugs.ruby-lang.org/
next parent reply other threads:[~2020-09-26 21:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 21:18 anthony [this message]
2020-10-15 15:18 ` [ruby-core:100404] [Ruby master Bug#17196] Segmentation Fault with Socket#close in Ractors ko1
2022-03-20 13:52 ` [ruby-core:107992] " 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-17196.20200926211858.44579@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).