-
Notifications
You must be signed in to change notification settings - Fork 416
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Passenger workers hang / segfault with Ruby 2.5 / concurrent-ruby 1.1.6 #871
Labels
bug
A bug in the library or documentation.
Comments
astupka
changed the title
Passenger worker hangs / segfaults with Ruby 2.5 / concurrent-ruby 1.1.6
Passenger workers hang / segfault with Ruby 2.5 / concurrent-ruby 1.1.6
May 15, 2020
Could be addressed in this PR #856 |
I've encountered the same issue with ruby 2.6.6, rails 5.2.4.3, and only when running unit tests with
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... |
#856 was merged plese test with master. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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)
The text was updated successfully, but these errors were encountered: