From: Eric Wong <normalperson@yhbt.net>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:89859] Re: [Ruby trunk Bug#15316] rb_postponed_job_register not thread-safe
Date: Mon, 19 Nov 2018 00:22:49 +0000 [thread overview]
Message-ID: <20181119002248.3zp4kib7sbl2dpyy@dcvr> (raw)
In-Reply-To: <redmine.journal-74917.20181119000711.4e213c3f65b385b2@ruby-lang.org>
takashikkbn@gmail.com wrote:
> Well, I seem to have introduced at least two deadlocks by
> that. I already fixed the first one, and I'm going to fix the
> second one
> http://ci.rvm.jp/results/trunk-mjit@silicon-docker/1467162.
>
> I'll take a deeper look when I come home today, but do you
> know who wakes up rb_sigwait_sleep and/or how the hang there
> could happen?
Any signal should wake it up...
If you can't solve it, can you wait until after the 11/22
developers meeting?
It's a small chance, but I really want to get Thread::Light
(auto-fiber) ready and into 2.6 (at least for Linux/FreeBSD),
and I barely have time for Ruby as it is.
It's not looking like I'll be able to afford to hack on Ruby
next year :<
next prev parent reply other threads:[~2018-11-19 0:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-15316.20181118044928@ruby-lang.org>
2018-11-18 4:49 ` [ruby-core:89848] [Ruby trunk Bug#15316] rb_postponed_job_register not thread-safe normalperson
2018-11-18 6:49 ` [ruby-core:89851] " Eric Wong
2018-11-18 8:09 ` [ruby-core:89852] " takashikkbn
2018-11-18 8:19 ` [ruby-core:89853] " Eric Wong
2018-11-18 8:40 ` [ruby-core:89854] " takashikkbn
2018-11-19 0:07 ` [ruby-core:89858] " takashikkbn
2018-11-19 0:22 ` Eric Wong [this message]
2018-11-19 0:52 ` [ruby-core:89860] " takashikkbn
2018-11-20 1:12 ` [ruby-core:89892] " takashikkbn
2018-11-30 5:19 ` [ruby-core:90186] " takashikkbn
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=20181119002248.3zp4kib7sbl2dpyy@dcvr \
--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).