From: josh.cheek@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:94419] [Ruby master Bug#16110] Doesn't detect deadlock on Ruby 2.4 and 2.5 on Windows
Date: Sun, 18 Aug 2019 20:09:12 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-16110.20190818200912.a9cae5bb59933216@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16110.20190818200912@ruby-lang.org
Issue #16110 has been reported by josh.cheek (Josh Cheek).
----------------------------------------
Bug #16110: Doesn't detect deadlock on Ruby 2.4 and 2.5 on Windows
https://bugs.ruby-lang.org/issues/16110
* Author: josh.cheek (Josh Cheek)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.5.5p157 (2019-03-15 revision 67260) [i386-mingw32]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
The following code is detected as a deadlock, except in Ruby 2.4 and 2.5 on Windows:
``` sh
ruby -r thread -ve 'Thread.new { Queue.new.shift }.join'
```
You can see it run in this code: https://github.com/JoshCheek/childprocess_experiment/blob/368052de8e433933035395216e8c48b8302b6fdf/Rakefile#L3
And it gets stuck in AppVeyor's CI because it doesn't realize it's deadlocked: https://ci.appveyor.com/project/JoshCheek/childprocess-experiment/build/job/3j06xan4ygm63ppd
--
https://bugs.ruby-lang.org/
next parent reply other threads:[~2019-08-18 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-16110.20190818200912@ruby-lang.org>
2019-08-18 20:09 ` josh.cheek [this message]
2019-08-19 14:28 ` [ruby-core:94435] [Ruby master Bug#16110] Doesn't detect deadlock on Ruby 2.4 and 2.5 on Windows Greg.mpls
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-16110.20190818200912.a9cae5bb59933216@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).