Xerces memory leak on Windows when deleting a parser --- Work around

2001-08-23 Thread David Bonnecaze
Hello, Found a solution to my memory leak problem. Again, this is strange as well. By setting the DOM_Document to 0 before deleting does the trick. Code example: int main(int argc, char* argv[]) { XMLPlatformUtils::Initialize(); DOMParser* parser = new DOMParser; parser->setValidationSch

Xerces memory leak on Windows when deleting a parser that the DOM_Document has been accessed

2001-08-23 Thread David Bonnecaze
Hello, Using Xerces 1.5.1 MS VC++ 6.0 sp5 window 2000 OS This I found to be very strange. In my testing to be able to open multiple xml files I found a memory leak that occurs once the DOM_Document is gotten from the DOMParser. Even though the DOMParser is reset and/or deleted, and the DOM_Docu

Xerces Memory Use on windows 2000 platform

2001-08-23 Thread David Bonnecaze
I am using Xerces 1.5.1 and find that quite a bit of memory is used and retained when parsing an xml file. The file I am using is about 1.6 meg and running a short program that only parses the file the memory usage is about 24 megs. This is in release mode. Does this seem correct? Should I be

Validation and Element insertion question

2001-08-15 Thread David Bonnecaze
My program reads in an xml data file that is validated against a DTD file. I am trying to migrate to xerces 1.5.1 to fix some of the performance and memory leak problems my program is experiencing. I am having 2 issues with the migration. 1. Validate an Element before adding it to the DOM. In