From: xtkoba+ruby@... Date: 2021-05-20T20:40:46+00:00 Subject: [ruby-core:103924] [Ruby master Bug#17875] Segfault when reusing a closed Fiber scheduler inside a Thread Issue #17875 has been updated by xtkoba (Tee KOBAYASHI). The symptom seems similar to that of #17618. ---------------------------------------- Bug #17875: Segfault when reusing a closed Fiber scheduler inside a Thread https://bugs.ruby-lang.org/issues/17875#change-92054 * Author: rmosolgo (Robert Mosolgo) * Status: Open * Priority: Normal * ruby -v: 3.0.1 * Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN ---------------------------------------- Hi! I've been trying to learn the new `Fiber.scheduler` API. I ran into this segfault when I was misusing scheduler instances in Minitest. I was able to reproduce the bug in isolation and I thought I'd share it here in case it's helpful to anyone. I attached the program as `scheduler_bug.rb` and the output in `bug_output.txt`. I expected this program to terminate with an error, but not with a segfault. If there's anything else I can do to help, please let me know! Thanks, Robert ---Files-------------------------------- scheduler_bug.rb (4.92 KB) bug_output.txt (24.1 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: