The XmlPlatformUtils::Initialize() description in the documentation: "Perform per-process parser initialization." This means you should call Initialize() once per process; likewise for Terminate(). Calling the functions multiple times in a process could cause the behavior you're seeing, especially if you're calling them from multiple threads.
-----Original Message----- From: 91change [mailto:91cha...@gmail.com] Sent: Wednesday, March 25, 2009 2:49 PM To: c-users@xerces.apache.org Subject: Memory Leaking in xerces-2.8.0 Please find my consttuctor and distructor XMLConfig::XMLConfig() { try { XMLPlatformUtils::Initialize(); } catch( XMLException& e ) { } m_ConfigFileParser = new XercesDOMParser; } XMLConfig::~XMLConfig() { try { // Terminate Xerces XMLPlatformUtils::Terminate(); } catch( xercesc::XMLException& e ) { } } i will create only 3 or 4 XMLConfig object and use different m_ConfigFileParser to parse multiple files .... (more than 10 ) m_ConfigFileParser->setErrorHandler(NULL); m_ConfigFileParser->setValidationScheme(XercesDOMParser::Val_Always); m_ConfigFileParser->setDoNamespaces( true); m_ConfigFileParser->setDoSchema( true); m_ConfigFileParser->setValidationSchemaFullChecking(true); m_ConfigFileParser->setDoValidation(true); cout<<endl<<"Before parse called"<<endl; m_ConfigFileParser->parse( configFile.c_str() ) I am getting a lot of memory leak .......How can i avoid that .... If i try to delete(m_ConfigFileParser) ...There is a segmentation fault happening ... Please help . -- View this message in context: http://www.nabble.com/Memory-Leaking-in-xerces-2.8.0-tp22707783p22707783 .html Sent from the Xerces - C - Users mailing list archive at Nabble.com.
