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
Illegal Instruction in active_support to_json call #21090
Comments
@sgringwe I suspect this may be a bug in ruby that has been fixed in the 2.2.1 or 2.2.2 patch releases - any chance you can upgrade so that we can rule that out. If it's not that then it must be related to the data being encoded - any chance of seeing what that is when you get the crash? |
Hi @pixeltrix - unfortunately after upgrading to 2.2.2 the issue is still present. i'll do my best to try and print out the json being encoded. |
@pixeltrix I have some example JSON from some errors but it contains some private data that might take a while to strip out. Is there any information you could add about what type of characters could cause this, or what type of encoding that is expected? |
Do you happen to know the type of object being encoded? |
@chancancode it is an active record object, if that's what you are referring to. unfortunately I don't know the specific value or object being encoded. Going to continue trying to get those details |
@chancancode This ended up being caused by sparklemotion/nokogiri#1332 (libxml conflciting with nokogiri and causing memory corruption). no issue with rails |
@sgringwe thanks for coming back and closing the issue - it's always helpful to know the resolution for ourselves and anyone else with similar problems. |
Rails 4.2.3. I am getting consistent but not replicatable yet crashes when calling to_json. This is crashing ruby itself, but the code causing the crash is in Active support and active record so I figured I'd post it here first. The error seems to end on string.rb in all cases. The most common case is this below, and happens dozens of times a day (1 per 2500 requests or so).
which all happen in a to_json call of some sort.
A different stacktrace to get to the same error much less often is:
The text was updated successfully, but these errors were encountered: