Valgrind continues to report 'definitely' lost bytes in
my application at the point where it calls the parent
class (XMLStream) parse() method.
When compiled to use libxml2 it suggests a memory leak
(through malloc) when calling xmlCreatePushParserCtxt
in XMLStream::parse(const char*).
It appears to be the only place where a memory leak is
reported in my application - and it is indeed leaking
memory. After a few days the daemon using this library
has consumed 50% of the memory on the machine - never
giving it back to the OS.
Could someone, somehow double check this for me? I am
running FC3 on a 2.6.12 kernel, g++ 3.4.4 the latest
version of libxml2 and common c++.
Log in to post a comment.