Bugs item #26013, was opened at 2009-05-24 20:34 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1971&aid=26013&group_id=494
Category: memory Group: None >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: Nobody (None) >Assigned to: Charlie Savage (cfis) Summary: Memory leak in Reader#read_string Initial Comment: I use libxml when I need to parse very large xml files. When pulling text from reader nodes, I usually navigate to the text node, read it's `.value` and skip its closing tag. On a new project, though, I tried using reader.read_string reader.next But, I noticed that it leaked a ton of memory. For example, after parsing a 64MB XML file, Ruby was using 611MB of RAM. After applying this patch, Ruby used less than 10MB to parse the file. ---------------------------------------------------------------------- >Comment By: Charlie Savage (cfis) Date: 2011-04-18 12:37 Message: Thanks for the report. This has been fixed in the latest release. Charlie ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1971&aid=26013&group_id=494 _______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
