[libxml-devel] Memory leak with 0.9.6 and 0.9.7

2009-01-07 Thread Joseph Palermo
We are using some code that utilizes libxml and creates XML documents. Using 0.9.5 everything is fine. Using 0.9.6 or 0.9.7, the more we use this code, the higher our memory usage gets. Seems likely that a memory leak was introduced in 0.9.6. We are seeing this same behavior on OS X and Gentoo.

Re: [libxml-devel] Memory leak with 0.9.6 and 0.9.7

2009-01-07 Thread Charlie Savage
Hi Joseph, We are using some code that utilizes libxml and creates XML documents. Using 0.9.5 everything is fine. Using 0.9.6 or 0.9.7, the more we use this code, the higher our memory usage gets. Seems likely that a memory leak was introduced in 0.9.6. We are seeing this same behavior on O

Re: [libxml-devel] Namespace issue with validate_schema?

2009-01-07 Thread Charlie Savage
This is likely a PEBKAC issue rather than a bug. I hope I'm submitting to the right list. I'm getting different validation results from libxml in Ruby than I am from a command-line tool (xmllint). I'm using a schema definition from ASTM to validate the output, for what it cost me the schema sho

Re: [libxml-devel] Memory leak with 0.9.6 and 0.9.7

2009-01-07 Thread Joseph Palermo
On Jan 7, 1:08 pm, Charlie Savage wrote: > Hi Joseph, > > > We are using some code that utilizes libxml and creates XML > > documents. Using 0.9.5 everything is fine. Using 0.9.6 or 0.9.7, the > > more we use this code, the higher our memory usage gets. > > > Seems likely that a memory leak wa

Re: [libxml-devel] Memory leak with 0.9.6 and 0.9.7

2009-01-07 Thread Joseph Palermo
On Jan 7, 1:38 pm, Joseph Palermo wrote: > On Jan 7, 1:08 pm, Charlie Savage wrote: > > > > > Hi Joseph, > > > > We are using some code that utilizes libxml and creates XML > > > documents. Using 0.9.5 everything is fine. Using 0.9.6 or 0.9.7, the > > > more we use this code, the higher our m

Re: [libxml-devel] Memory leak with 0.9.6 and 0.9.7

2009-01-07 Thread Charlie Savage
Hi Joseph, I'll see if I can put something together, we know it's in the to_solr_doc from acts_as_solr somewhere. Looks like the problem is in to_s on Node 1.times do node = XML::Node.new 'node' node.to_s end Nice work - that's a great test case. So if I I run this code: 1000.

Re: [libxml-devel] Memory leak with 0.9.6 and 0.9.7

2009-01-07 Thread Charlie Savage
Looks like the problem is in to_s on Node 1.times do node = XML::Node.new 'node' node.to_s end Anyway, will have to look and see if there is anything obvious in the part of the bindings. And fixed in trunk. It was caused by the addition of encoding support in the last couple of

Re: [libxml-devel] Memory leak with 0.9.6 and 0.9.7

2009-01-07 Thread Joseph Palermo
On Jan 7, 4:06 pm, Charlie Savage wrote: > Hi Joseph, > > >> I'll see if I can put something together, we know it's in the > >> to_solr_doc from acts_as_solr somewhere. > > > Looks like the problem is in to_s on Node > > > 1.times do > > node = XML::Node.new 'node' > > node.to_s > > end

Re: [libxml-devel] Memory leak with 0.9.6 and 0.9.7

2009-01-07 Thread Aaron Patterson
2009/1/7 Charlie Savage : > Hi Joseph, > >>> I'll see if I can put something together, we know it's in the >>> to_solr_doc from acts_as_solr somewhere. >> >> Looks like the problem is in to_s on Node >> >> 1.times do >> node = XML::Node.new 'node' >> node.to_s >> end > > Nice work - that's a

Re: [libxml-devel] Memory leak with 0.9.6 and 0.9.7

2009-01-07 Thread Charlie Savage
Hey Aaron, Looks like the xmlOutputBufferPtr never gets freed. Yup, exactly right. I posted a fix to trunk and sent another email to the list, but somehow it never made it through. Index: ext/libxml/ruby_xml_node.c === --- ex