[ruby-core:114515] [Ruby master Bug#17826] Ractor#take hangs if used in multiple Threads
From:
"jeremyevans0 (Jeremy Evans) via ruby-core" <ruby-core@...>
Date:
2023-08-24 21:32:15 UTC
List:
ruby-core #114515
Issue #17826 has been updated by jeremyevans0 (Jeremy Evans).
Status changed from Assigned to Closed
This appears fixed in Ruby 3.3.0-preview1, though it doesn't work in Ruby 3.2.2.
----------------------------------------
Bug #17826: Ractor#take hangs if used in multiple Threads
https://bugs.ruby-lang.org/issues/17826#change-104310
* Author: kukunin (Sergiy Kukunin)
* Status: Closed
* 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/
______________________________________________
ruby-core mailing list -- [email protected]
To unsubscribe send an email to [email protected]
ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/