Swatilekha Doloi wrote:
This isn't a valid test. You should use the Visual Studio heap debugging features if you think Xerces-C is leaking memory:I do not have any memory tools. It's just the task manager in Windows that I'm using. I checked the usage values at the breakpoints (set before and after the function calls).
http://msdn.microsoft.com/en-us/library/e5ewb1h3%28VS.80%29.aspx FWIW, I don't see any memory leaks with your scenario. Dave