On Wed, 29 Aug 2007 01:36:00 +0100, Dan Janowski <[EMAIL PROTECTED]> wrote:
> Hi all, > > I am going to go out on a limb and say, tentatively, that my new > approach to memory management is working. It is so far only applied > to the ruby side of tree.c functions (ruby_xml_node...). My simple > example of creating the same document 1M times, loosing references to > the priors and watching the mark and free run, is at least no worse. > Sounds cool! > Since I have not propagated the changes to other parts, the test > suite is broken. I suspect that they did not expose the memory > problems anyway. > > What I need now is a few concise examples that have blown up > previously. I am particularly looking for ones that just use the node > operations. > You're right that the unit tests don't really hit the memory bugs, but there's also a few additional tests in there that specifically test some of the difficult areas (node copying, etc). They're especially useful with valgrind. Cheers, -- Ross Bamford - [EMAIL PROTECTED] _______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
