Stephen Collyer wrote:
I'm seeing the following possible memory leak from valgrind:
==30248== 9,556 bytes in 246 blocks are possibly lost in loss record 123 of 131
==30248== at 0x4022FCC: operator new(unsigned) (in
/usr/lib/valgrind/x86-linux/vgpreload_memcheck.so)
==30248== by 0x51AF671: xercesc_2_7::MemoryManagerImpl::allocate(unsigned)
(in /usr/lib/libxerces-c.so.27.0)
==30248== by 0x527A2B0: xercesc_2_7::XMemory::operator new(unsigned) (in
/usr/lib/libxerces-c.so.27.0)
==30248== by 0x516FD43:
xercesc_2_7::DatatypeValidatorFactory::initCanRepRegistory() (in
/usr/lib/libxerces-c.so.27.0)
==30248== by 0x517205D:
xercesc_2_7::DatatypeValidatorFactory::expandRegistryToFullSchemaSet() (in
/usr/lib/libxerces-c.so.27.0)
==30248== by 0x51F5154:
xercesc_2_7::SchemaGrammar::SchemaGrammar(xercesc_2_7::MemoryManager*) (in
/usr/lib/libxerces-c.so.27.0)
==30248== by 0x51A5195:
xercesc_2_7::IGXMLScanner::resolveSchemaGrammar(unsigned short const*, unsigned
short const*) (in /usr/lib/libxerces-c.so.27.0)
==30248== by 0x51A5BE3:
xercesc_2_7::IGXMLScanner::parseSchemaLocation(unsigned short const*) (in
/usr/lib/libxerces-c.so.27.0)
==30248== by 0x519A0D2: xercesc_2_7::IGXMLScanner::scanStartTagNS(bool&) (in
/usr/lib/libxerces-c.so.27.0)
==30248== by 0x519C5E3: xercesc_2_7::IGXMLScanner::scanContent() (in
/usr/lib/libxerces-c.so.27.0)
==30248== by 0x519C7EE:
xercesc_2_7::IGXMLScanner::scanDocument(xercesc_2_7::InputSource const&) (in
/usr/lib/libxerces-c.so.27.0)
==30248== by 0x51DD974:
xercesc_2_7::SAX2XMLReaderImpl::parse(xercesc_2_7::InputSource const&) (in
/usr/lib/libxerces-c.so.27.0)
Does anyone know if this is anything to worry about ?
Are you calling XMLPlatformUtils::Terminate() before your application exits?
Dave
