From: Daniel Veillard (Daniel.Veillard@w3.org)
Date: Wed May 03 2000 - 03:55:50 EDT
On Tue, May 02, 2000 at 04:47:39PM -0400, Bernie Rosman wrote:
>
> Daniel,
>
> We seem to be seeing a possible memory leak when using libxml-1.8.7 for
> a sequence of several (10-100) xmlParseMemory calls. We do not see this
> leak in our previous version which uses libxml-1.7.3. Between each call,
> the code calls xmlFreeDoc and frees the memory that we allocated. In the
> new version (using 1.8.7), I added a call to xmlCleanupParser, but that
> did not seem to help. Is there some other function new to libxml-1.8.7
> that I should be calling when using xmlParseMemory?
Hum interesting ...
I run all my regression tests with memory debugging activated (in
xmlmemory.h), but I don't think I test automatically parsing through
xmlParseMemory(). The bug is probably located in that section or nearby,
not in the generic parsing code (though i have cleaned up some
memory leaks in the transition to 2.0, mostly leaks occuring when
there was parsing errors).
The simplest is probably to add a --memory option to xmllint.c
(tester.c in libxml-1.x) and add this to the regression tests.
I will try to look at it,
Daniel
-- Daniel.Veillard@w3.org | W3C, INRIA Rhone-Alpes | Today's Bookmarks : Tel : +33 476 615 257 | 655, avenue de l'Europe | Linux XML libxml WWW Fax : +33 476 615 207 | 38330 Montbonnot FRANCE | Gnome rpm2html rpmfind http://www.w3.org/People/all#veillard%40w3.org | RPM badminton Kaffe ---- Message from the list xml@xmlsoft.org Archived at : http://xmlsoft.org/messages/ to unsubscribe: echo "unsubscribe xml" | mail majordomo@xmlsoft.org
This archive was generated by hypermail 2b29 : Wed Aug 02 2000 - 12:30:11 EDT