[ https://issues.apache.org/jira/browse/XERCESC-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Kolpackov closed XERCESC-333. ----------------------------------- Resolution: Fixed Assignee: (was: Xerces-C Developers Mailing List) Assuming fixed in 3.0.1. > memory leak parsing xml document > -------------------------------- > > Key: XERCESC-333 > URL: https://issues.apache.org/jira/browse/XERCESC-333 > Project: Xerces-C++ > Issue Type: Bug > Components: Non-Validating Parser > Affects Versions: 1.7.0 > Environment: Operating System: Solaris > Platform: Sun > Reporter: Lorna Jones > > I have built a simple xml SAX(2) parsing visual interface using Xerces. I > pass > in an XML file, and Xerces Parses it fine... except when I close down my > application it shows me that I have memory leaks. I have traced this back to > the lines of code (the one mared with # being the specific problem).. > " try //parsing the document... > { > CHandler handler(encodingName,unRepFlags,expandNamespaces); > parser->setContentHandler(&handler); > parser->setErrorHandler(&handler); > # parser->parse(xmlFile); > } > " > The memory leaks appear to be text data of that of the xml file. e.g.. > " The thread 0xE2 has exited with code 0 (0x0). > Detected memory leaks! > Dumping objects -> > c:\program files\microsoft visual studio\vc98\include\crtdbg.h(552) : {12875} > normal block at 0x0036E960, 13 bytes long. > Data: <cml:molecule > 63 6D 6C 3A 6D 6F 6C 65 63 75 6C 65 00 > c:\program files\microsoft visual studio\vc98\include\crtdbg.h(552) : {12873} > normal block at 0x0036E9F0, 9 bytes long. > Data: <molecule > 6D 6F 6C 65 63 75 6C 65 00 > .... etc etc > c:\program files\microsoft visual studio\vc98\include\crtdbg.h(552) : {979} > normal block at 0x00310EC0, 35 bytes long. > Data: <http://www.xml-c> 68 74 74 70 3A 2F 2F 77 77 77 2E 78 6D 6C 2D 63 > The thread 0x14A has exited with code 0 (0x0). > The program 'D:\Genesis32 > \Chemistry\ChemTech\Prototypes\visualTry\VisualCML\Debug\VisualCML.exe' has > exited with code 0 (0x0). > The only thing I can think of is there is a pointer which is being declared > as > new but not being deleted at the end of its use. > or perhaps a destroy XMLReader function? > I am still pretty new to C++ and am not sure exactly the best eway to resolve > this problem. > Best of Luck :o) > cheers > Lorna -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org