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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
worker crashes (and dump backtrace) after fork #100
Comments
let me try to update gems first |
Alright, so I can't be certain, but there are some evidence that this may be one of the two weakmap bugs: Likely the first one given you are not compacting? What suggest this is:
I'd suggest upgrading to Ruby 3.2.3 which should contain these fixes, or to 3.3.0. |
Also note to self: I should detect these broken versions, issue a warning and disable |
wow, thanks for the quick and helpful suggestion! Let me also try to upgrade Ruby and report then! |
Done in #101 |
UPDATE: We have upgraded our deployments to Ruby 3.2.3 and we see no crash so far 馃憤 (I'll keep eyes on it for another 1-2 days) |
That's great to hear! Closing for now then, but let me know if you run into another issue. Is #99 solved too? Perhaps it was the same root cause but with different symptoms? |
@casperisfine Thanks for your great support every time. |
馃檱 |
Hi again,
sorry for creating issues repeatedly 馃檹
At the same time of #99, we also see the errors below:
I'm not used to read this kinda traces, but it seems that the handler around fork for redis-client or concurrent_ruby is somehow weird?
Environment:
Linux 5.10.210-201.852.amzn2.x86_64 ...
Stacktrace
NOTE that the log is ordered by timestamp desc.
The text was updated successfully, but these errors were encountered: