Open astupka opened 4 years ago
Could be addressed in this PR https://github.com/ruby-concurrency/concurrent-ruby/pull/856
I've encountered the same issue with ruby 2.6.6, rails 5.2.4.3, and only when running unit tests with fork
call.
[BUG] Segmentation fault at 0x00007f685c9559d0 ruby 2.6.6p146 (2020-03-31 revision 67876) [x86_64-linux]
When rolling back this gem to 1.1.5, the Segmentation Fault disappears.
UPDATE: with 1.1.5 the Segmentation Fault may still be there...
Thank you for all your hard work on the latest 1.1.6 release.
I recently upgraded our app gems and started noticing the passenger workers would become unresponsive (request queue = 100) and not shutdown (normal mem/no CPU usage) after ~12-24 hours. Inspecting the error logs, I found some segfaults that appeared related to the finalization code present in 1.1.6 and a possible MRI bug. Rolling back this single gem to 1.1.5 resolved the issue.
Initial segfault data (let me know if the rest would be helpful)