-
-
Notifications
You must be signed in to change notification settings - Fork 901
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
segfault on add_child_node when GC enabled #1007
Comments
Once in a while, instead of a segfault, ruby throws an exception:
When I inspect the value of the object that must be a |
I currently think this is a Representable-specific issue, so I'm closing the ticket. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following code snippet will (almost always) cause a segfault after calling add_child_node when ruby garbage collection is enabled:
https://gist.github.com/7602296
I've tested this on Nokogiri 1.6.0 using libxml2 2.8.0 and 2.9.1. Disabling GC prevents the segfault from occurring.
I'd like to isolate the issue further, but I'm not sure where to dig in next. Any ideas on how to approach this?
The text was updated successfully, but these errors were encountered: