Thank for your reply but :<br><br>I put<br> xmlInitParser(); <br><br>at the begining<br>and<br> xmlCleanupThreads();<br> xmlCleanupParser();<br>just before exit;<br><br><br>when i make a test with valgrind i do a test with 1 request and another with 5 requests and compare valgrind output.<br>
i'm oblige for the moment to use 2.6.x version of libxml2 ...<br><br>Regards<br><br>Olivier<br><br><br><br><br><div class="gmail_quote">On Wed, Nov 23, 2011 at 7:30 PM, Debian Bug Tracking System <span dir="ltr"><<a href="mailto:owner@bugs.debian.org">owner@bugs.debian.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">This is an automatic notification regarding your Bug report<br>
which was filed against the libxml2 package:<br>
<br>
#649745: libxml2: memory leak when use xmlDocDumpFormatMemoryEnc in a multithread daemon<br>
<br>
It has been closed by Mike Hommey <<a href="mailto:mh@glandium.org">mh@glandium.org</a>>.<br>
<br>
Their explanation is attached below along with your original report.<br>
If this explanation is unsatisfactory and you have not received a<br>
better one in a separate message then please contact Mike Hommey <<a href="mailto:mh@glandium.org">mh@glandium.org</a>> by<br>
replying to this email.<br>
<font color="#888888"><br>
<br>
--<br>
649745: <a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649745" target="_blank">http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649745</a><br>
Debian Bug Tracking System<br>
Contact <a href="mailto:owner@bugs.debian.org">owner@bugs.debian.org</a> with problems<br>
</font><br><br>---------- Forwarded message ----------<br>From: Mike Hommey <<a href="mailto:mh@glandium.org">mh@glandium.org</a>><br>To: olivier chirossel <<a href="mailto:olivier.chirossel@gmail.com">olivier.chirossel@gmail.com</a>>, <a href="mailto:649745-done@bugs.debian.org">649745-done@bugs.debian.org</a><br>
Date: Wed, 23 Nov 2011 19:27:08 +0100<br>Subject: Re: [xml/sgml-pkgs] Bug#649745: libxml2: memory leak when use xmlDocDumpFormatMemoryEnc in a multithread daemon<br>On Wed, Nov 23, 2011 at 07:10:19PM +0100, olivier chirossel wrote:<br>
> Package: libxml2<br>
> Version: 2.7.8.dfsg-5<br>
> Severity: important<br>
><br>
> Dear Maintainer,<br>
> *** Please consider answering these questions, where appropriate ***<br>
><br>
> * What led up to the situation?<br>
> * What exactly did you do (or not do) that was effective (or<br>
> ineffective)?<br>
> * What was the outcome of this action?<br>
> * What outcome did you expect instead?<br>
><br>
> *** End of the template - remove these lines ***<br>
><br>
><br>
> -- System Information:<br>
> Debian Release: wheezy/sid<br>
> APT prefers unstable<br>
> APT policy: (500, 'unstable')<br>
> Architecture: amd64 (x86_64)<br>
><br>
> Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)<br>
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8)<br>
> Shell: /bin/sh linked to /bin/dash<br>
><br>
> Versions of packages libxml2 depends on:<br>
> ii libc6 2.13-21<br>
> ii zlib1g 1:1.2.3.4.dfsg-3<br>
><br>
> Versions of packages libxml2 recommends:<br>
> ii xml-core 0.13<br>
><br>
> libxml2 suggests no packages.<br>
><br>
> -- no debconf information<br>
><br>
> valgrind trace<br>
><br>
> ==9688== 968 bytes in 1 blocks are definitely lost in loss record 35 of 63<br>
> ==9688== at 0x4C2779D: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)<br>
> ==9688== by 0x50F2D11: xmlGetGlobalState (threads.c:584)<br>
> ==9688== by 0x50F21B4: __xmlDefaultBufferSize (globals.c:814)<br>
> ==9688== by 0x50A4A52: xmlBufferCreate (tree.c:6870)<br>
> ==9688== by 0x50AB89C: xmlAllocOutputBuffer (xmlIO.c:2320)<br>
> ==9688== by 0x5158382: xmlDocDumpFormatMemoryEnc (xmlsave.c:2286)<br>
> ==9688== by 0x416935: admin_function (admin.c:205)<br>
> ==9688== by 0x4E33B3F: start_thread (pthread_create.c:304)<br>
<br>
That wouldn't happen if your program used xmlCleanupThreads at the end,<br>
which it should.<br>
<br>
Mike<br>
<br>
<br><br>---------- Forwarded message ----------<br>From: olivier chirossel <<a href="mailto:olivier.chirossel@gmail.com">olivier.chirossel@gmail.com</a>><br>To: Debian Bug Tracking System <<a href="mailto:submit@bugs.debian.org">submit@bugs.debian.org</a>><br>
Date: Wed, 23 Nov 2011 19:10:19 +0100<br>Subject: libxml2: memory leak when use xmlDocDumpFormatMemoryEnc in a multithread daemon<br>Package: libxml2<br>
Version: 2.7.8.dfsg-5<br>
Severity: important<br>
<br>
Dear Maintainer,<br>
*** Please consider answering these questions, where appropriate ***<br>
<br>
* What led up to the situation?<br>
* What exactly did you do (or not do) that was effective (or<br>
ineffective)?<br>
* What was the outcome of this action?<br>
* What outcome did you expect instead?<br>
<br>
*** End of the template - remove these lines ***<br>
<br>
<br>
-- System Information:<br>
Debian Release: wheezy/sid<br>
APT prefers unstable<br>
APT policy: (500, 'unstable')<br>
Architecture: amd64 (x86_64)<br>
<br>
Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)<br>
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8)<br>
Shell: /bin/sh linked to /bin/dash<br>
<br>
Versions of packages libxml2 depends on:<br>
ii libc6 2.13-21<br>
ii zlib1g 1:1.2.3.4.dfsg-3<br>
<br>
Versions of packages libxml2 recommends:<br>
ii xml-core 0.13<br>
<br>
libxml2 suggests no packages.<br>
<br>
-- no debconf information<br>
<br>
valgrind trace<br>
<br>
==9688== 968 bytes in 1 blocks are definitely lost in loss record 35 of 63<br>
==9688== at 0x4C2779D: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)<br>
==9688== by 0x50F2D11: xmlGetGlobalState (threads.c:584)<br>
==9688== by 0x50F21B4: __xmlDefaultBufferSize (globals.c:814)<br>
==9688== by 0x50A4A52: xmlBufferCreate (tree.c:6870)<br>
==9688== by 0x50AB89C: xmlAllocOutputBuffer (xmlIO.c:2320)<br>
==9688== by 0x5158382: xmlDocDumpFormatMemoryEnc (xmlsave.c:2286)<br>
==9688== by 0x416935: admin_function (admin.c:205)<br>
==9688== by 0x4E33B3F: start_thread (pthread_create.c:304)<br>
<br>
<br>
<br></blockquote></div><br>