From: Eric Wong <e@80x24.org>
To: spew@80x24.org
Subject: [PATCH 1/2] test_fiber: show crash on GC after forking
Date: Sun, 9 Sep 2018 08:00:30 +0000 [thread overview]
Message-ID: <20180909080031.6527-1-e@80x24.org> (raw)
But the management of stacks for root fiber and regular
fibers is different and confusing. Perhaps unifying
thread and fiber stack cache is the best way to go.
Is a separate class of stacks even necessary?
We should aim to minimize use of stack space.
"[BUG] Illegal root fiber parameter"
---
test/ruby/test_fiber.rb | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/test/ruby/test_fiber.rb b/test/ruby/test_fiber.rb
index c835246fda..d481117259 100644
--- a/test/ruby/test_fiber.rb
+++ b/test/ruby/test_fiber.rb
@@ -271,7 +271,16 @@ def test_fork_from_fiber
assert_nothing_raised(bug5700) do
Fiber.new do
pid = fork do
- Fiber.new {}.transfer
+ Fiber.new {
+ pid = fork do
+ 10000.times do
+ Fiber.new {}.transfer
+ f2 = Fiber.new {
+ Fiber.yield
+ }
+ end
+ end
+ }.transfer
end
end.resume
end
--
EW
next reply other threads:[~2018-09-09 8:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-09 8:00 Eric Wong [this message]
2018-09-09 8:00 ` [PATCH 2/2] wip Eric Wong
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=20180909080031.6527-1-e@80x24.org \
--to=e@80x24.org \
--cc=spew@80x24.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).