Closed dorianmarie closed 8 months ago
A duplicate of https://github.com/ruby-concurrency/concurrent-ruby/issues/1023 Also if you are not using concurrent-ruby-ext, then the segfault cannot be an issue of concurrent-ruby.
Ok FYI I created a minimal rails app with this crash: https://github.com/dorianmarie/rails-segmentation-fault-minimal I think it's related to concurrent ruby usage in rails
It is not, it's a CRuby bug: https://bugs.ruby-lang.org/issues/20085
concurrent-ruby just does Fiber#resume
which is perfectly valid.
Ah thanks
I have a crash related to concurrent-ruby, trying to reduce to a minimal app