[xml] memory leak in __xmlGenericErrorContext, according to Valgrind
- From: Albert Zeyer <albert zeyer rwth-aachen de>
- To: xml gnome org
- Subject: [xml] memory leak in __xmlGenericErrorContext, according to Valgrind
- Date: Fri, 22 May 2009 19:11:58 -0000
Hi,
Valgrind just always gives this report:
==10130== 512 bytes in 1 blocks are definitely lost in loss record 5
of 6
==10130== at 0x40253BA: malloc (vg_replace_malloc.c:207)
==10130== by 0x4B52357: (within
/usr/lib/opengl/nvidia/lib/libGL.so.180.51)
==10130== by 0x41A209B: __xmlGenericErrorContext (globals.c:876)
==10130== by 0x8318FB1: StripHtmlTags(stlpd_std::basic_string<char,
stlpd_std::char_traits<char>, stlpd_std::allocator<char> > const&)
(StringUtils.cpp:721)
In that StripHtmlTags function in the specific line, I am doing this
call:
xmlSetStructuredErrorFunc(NULL, &xmlErrorHandlerDummy);
Can somebody confirm this or make it a false alarm?
I looked a bit through the libxml2 code. There is no malloc in
__xmlGenericErrorContext but I guess it was inlined from
xmlNewGlobalState. So, if Valgrind is right, it means that
xmlFreeGlobalState isn't called in all cases.
PS: Please CC me on any answer because I am not registered in the list.
Thanks a lot,
Albert
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]