From: "luke-gru (Luke Gruber) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "luke-gru (Luke Gruber)" <noreply@ruby-lang.org>
Subject: [ruby-core:122459] [Ruby Bug#21400] rb_bug() hit when killing current root fiber on non-main thread
Date: Thu, 05 Jun 2025 15:30:31 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-113647.20250605153030.3573@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-21400.20250605152438.3573@ruby-lang.org>
Issue #21400 has been updated by luke-gru (Luke Gruber).
I created a PR: https://github.com/ruby/ruby/pull/13526
----------------------------------------
Bug #21400: rb_bug() hit when killing current root fiber on non-main thread
https://bugs.ruby-lang.org/issues/21400#change-113647
* Author: luke-gru (Luke Gruber)
* Status: Open
* ruby -v: 3.5.0dev
* Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN
----------------------------------------
This following code hits an `rb_bug`:
```ruby
Thread.new { Fiber.current.kill }.join
```
Normally fibers gracefully handle this case by terminating and switching to another fiber, but if there is no other fiber it raises the `FIBER_FATAL_FIBER_KILLED` error and this is not caught by the starting thread, resulting in a bug.
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/
prev parent reply other threads:[~2025-06-05 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 15:24 [ruby-core:122458] " luke-gru (Luke Gruber) via ruby-core
2025-06-05 15:30 ` luke-gru (Luke Gruber) via ruby-core [this message]
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-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-113647.20250605153030.3573@ruby-lang.org \
--to=ruby-core@ml.ruby-lang.org \
--cc=noreply@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 NNTP newsgroup(s).