-
Notifications
You must be signed in to change notification settings - Fork 955
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
SIGSEGV since updating to Ruby 2.1 #616
Comments
I know this isn't much to go on at all - hoping that others who are experiencing this will see this and comment, see if there's a common factor. |
This appears to be an issue with how rollbar is trying to wrap DJ error reporting. I suspect this doesn't do what they think it does: |
Interesting. Worked under Ruby 2.0. cc @brianr It's not easy for me to have Rails pull in the rollbar gem but omit it from delayedjob, but I'll have a go and see if that resolves things. |
Hm, looks like this might be caused by this bug in ruby: https://bugs.ruby-lang.org/issues/9315 - looks like there is a fix ready for whenever 2.1.1 is released. @albus522 very possible; this code is over a year old and I don't remember exactly what the line is supposed to do. Is the example here the recommended way to add global error reporting for delayed_job? http://www.salsify.com/blog/delayed-jobs-callbacks-and-hooks-in-rails |
Confirmed. Bug does not present when the delayed_job rollbar hook is removed (https://github.com/bikeexchange/rollbar-gem/tree/FixDJReporting) Closing this & raising a new issue over in rollbar. Thanks for your help! |
@brianr that should work |
Looks like it's occuring on line 125 of
delayed/backend/base.rb
:So, I'm guessing some fun deserialisation stuff.
Ruby trace follows:
The text was updated successfully, but these errors were encountered: