Bugs item #19259, was opened at 2008-04-02 02:33 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1971&aid=19259&group_id=494
Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Joe Khoobyar (walltndr) Assigned to: Nobody (None) Summary: Calling remove! on a node causes memory leaks. Initial Comment: Nodes w/o a parent (i.e., due to calling remove!) will never be garbage collected because of a (typo?) mistaken && instead of || when checking the parent and the doc for NULL. Calling remove! never sets the doc to NULL. In fact, you'd be hard pressed to find anywhere in libxml2 or libxml-ruby where the doc pointer is explicitly set to NULL. See patch #19257 for the easy solution. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1971&aid=19259&group_id=494 _______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
