Skip to content

Issues: sparklemotion/nokogiri

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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
8 Open 75 Closed
8 Open 75 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

clone_node() doesn't duplicate nonstandard tag names topic/gumbo Gumbo HTML5 parser topic/memory Segfaults, memory leaks, valgrind testing, etc.
#3099 opened Jan 16, 2024 by stevecheckoway
@stevecheckoway
1
RFC: limit libgumbo memory allocations for untrusted HTML5 content topic/gumbo Gumbo HTML5 parser topic/memory Segfaults, memory leaks, valgrind testing, etc. topic/rfc
#2949 opened Aug 9, 2023 by flavorjones v1.19.0
1
optimization: consider alternative document free mechanisms that will allow setting RUBY_TYPED_FREE_IMMEDIATELY topic/memory Segfaults, memory leaks, valgrind testing, etc.
#2822 opened Mar 7, 2023 by flavorjones v1.19.0
1
explore: make NodeSet a subclass of Array topic/memory Segfaults, memory leaks, valgrind testing, etc.
#2184 opened Feb 1, 2021 by flavorjones v1.19.0
2
[bug] Memory is leaked when raising an exception from a custom XPath function, or from some SAX handler callbacks topic/error-handling topic/memory Segfaults, memory leaks, valgrind testing, etc.
#2097 opened Oct 13, 2020 by flavorjones v1.19.0
1
Clean up error handling in the C extension. topic/memory Segfaults, memory leaks, valgrind testing, etc.
#2096 opened Oct 12, 2020 by flavorjones • Draft v1.19.0
9
explore using AddressSanitizer in CI instead of (or in addition to) Valgrind topic/ci topic/memory Segfaults, memory leaks, valgrind testing, etc.
#2067 opened Aug 25, 2020 by flavorjones
2
too large memory footprint in READER node.attributes when millions of child nodes are present topic/memory Segfaults, memory leaks, valgrind testing, etc. topic/performance
#1283 opened May 8, 2015 by robert-v-simon v1.19.0
2
ProTip! Updated in the last three days: updated:>2024-12-24.