[libxml-devel] memory leak?

[Dan Janowski]

That version has all of the really bad leaks taken care of. There is a  
more recent version in SVN, but it is not in an RC state, which may be  
a few more days. It has a few more fixes, including some to XPath.

I'll announce the update, hopefully soon.

Dan

On Dec 18, 2007, at 08:49, simon.wilkinson at 434wireless.com wrote:

> I am running version 0.5.2.0.
>
> Simon
>
> Depends on the version you are running.
>
> ruby -e 'require "xml/libxml"; puts XML::Parser::VERSION'
>
> On Dec 17, 2007, at 18:47, simon.wilkinson at 434wireless.com wrote:
>
>> Hi,
>>
>> I have an application that reads a listing of files from a
>> directory, and then uses libxml-ruby (using XPath) to parse the
>> files.  This occurs in a loop, picking up new files as they are
>> added.  Over time, memory really grows on the process doing this
>> work.  Are there any known memory issues with the gem, or with using
>> XPath to do parsing?
>>
>> Thanks,
>>
>> Simon
>> _______________________________________________
>> libxml-devel mailing list
>> libxml-devel at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/libxml-devel
>
> _______________________________________________
> libxml-devel mailing list
> libxml-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/libxml-devel
> _______________________________________________
> libxml-devel mailing list
> libxml-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/libxml-devel