From: "ko1 (Koichi Sasada)" <noreply@...>
Date: 2021-12-14T16:29:05+00:00
Subject: [ruby-core:106665] [Ruby master Bug#17826] Ractor#take hangs if used in multiple Threads

Issue #17826 has been updated by ko1 (Koichi Sasada).


Yes, now it doesn't work correctly. Sorry I'll try to fix this issue on Ruby 3.2.

----------------------------------------
Bug #17826: Ractor#take hangs if used in multiple Threads
https://bugs.ruby-lang.org/issues/17826#change-95337

* Author: kukunin (Sergiy Kukunin)
* Status: Assigned
* Priority: Normal
* Assignee: ko1 (Koichi Sasada)
* ruby -v: ruby 3.0.1p64 (2021-04-05 revision 0fb782ee38) [x86_64-linux]
* Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN
----------------------------------------
Hello there. 

I was playing with Ractors (the awesome technology and the big leap for Ruby) and encountered weird behavior.

I tried to schedule and run Ractors in multiple threads, and found out, that Ractor#take hangs even if the ractor is finished.

Here is code to reproduce:


``` ruby
Array.new(2) do |n|
  Thread.new do
    r = Ractor.new do
      sleep 0.001
    end
    r.take
    puts "thread #{n} finished"
  end
end.each(&:join)

puts 'done'

```

The output is just "thread 0 finished" and the process hangs forever. Sometimes the second thread exists first, and the first freezes.

Thank you for your time. Hopefully, it's a valid bug report, not me just misusing the feature =)



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>