From: "wanabe (_ wanabe)" <noreply@...>
Date: 2022-03-21T06:47:18+00:00
Subject: [ruby-core:107996] [Ruby master Bug#17529] Ractor Segfaults with GC enabled

Issue #17529 has been updated by wanabe (_ wanabe).


I guess that the btest failure of ruby_3_0 branch on icc-x64 env may be fixed by `git cherry-pick d0d6227a0da5925acf946a09191f172daf53baf2 fff1edf23ba28267bf57097c269f7fa87530e3fa`.
(An example of this failure is http://rubyci.s3.amazonaws.com/icc-x64/ruby-3.0/log/20220321T004434Z.log.html.gz#test.rb)

----------------------------------------
Bug #17529: Ractor Segfaults with GC enabled
https://bugs.ruby-lang.org/issues/17529#change-96949

* Author: prajjwal (Prajjwal Singh)
* Status: Assigned
* Priority: Normal
* Assignee: ko1 (Koichi Sasada)
* ruby -v: ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x86_64-linux]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN
----------------------------------------
I've been benchmarking `Ractor` on my machine with the following naive prime number generator:

```ruby
# frozen_string_literal: true

def prime?(n)
  2.upto(n - 1).none? { |i| n % i == 0 }
end

NUM_WORKERS = ARGV[0].to_i

producer = Ractor.new do
  i = 1000000

  loop { Ractor.yield i; i += 1 }
end

workers = (1..NUM_WORKERS).map do
  Ractor.new producer do |producer|
    while n = producer.take
      Ractor.yield [n, prime?(n)]
    end
  end
end

loop do
  _r, ( number, prime ) = Ractor.select(*workers)

  p number if prime
end
```

The code inevitably segfaults, and it appears to be the garbage collector.

If I stick `GC.disable` in there, the code happily chugs along for several minutes on end without a problem.

---Files--------------------------------
ractor.crash (22.5 KB)


-- 
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>