-
Notifications
You must be signed in to change notification settings - Fork 143
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
Segmentation faults #159
Comments
Thanks for the report. Can you please provide a runnable reduced test case that I can use to reproduce this issue? It's unlikely that Sanitize itself is causing the segmentation fault since Sanitize is pure Ruby. It's much more likely to be a bug in a dependency or in Ruby itself, but without a test case I can run to reproduce the issue, I don't have any way to investigate this. |
Totally fair point, and I haven’t been able to reproduce in a test app. Not sure what might be going on. I’ll just close this issue now, and if anyone else encounters something similar they can probably find this via search. But for now, I think we can leave it be. Cheers! |
@rgrove It was probably caused by nokogumbo 1.4.10. I just reproduced it on my laptop
|
We’re using gem version 4.4.0 in production. I realized that my application was using the deprecated
clean
syntax, and wanted to run a quick sanity check before changing it tofragment
, so I tried the following:To my surprise, this reliably causes a segmentation fault!
Here is another dump:
...and a third for good measure:
Let me know if there is anything I can do to provide whatever additional information may be helpful.
The text was updated successfully, but these errors were encountered: