RE: Memory leaks...

["Arnold, Curt" <Cu...@hyprotech.com>]

Kommu R wrote on xerces-dev:
I was wondering if xercex 1.1.0 has memory leaks. 
Please advice me on this as to how do i take care to avoid them.
------

Xerces-C has some fairly well known memory leaks on shutdown, but no known leaks during processing.  Basically, there are a few tables that are not cleaned up due to a lack of a reliable automatic
mechanism to make sure that the code is not reentered after cleanup.  An explicit Uninitialize call was being considered to free those last resources.  The Mailing list archive has more discussions
than we would like to reproduce on that.

Also, the Xerces-dev mailing list has been replaced with separate mailing lists for Xerces-J and Xerces-C.  Check the mailing list page to see how to subscribe to the new lists.

Re: Memory leaks...

[Tom Jordahl <to...@allaire.com>]

"Arnold, Curt" wrote:
> Xerces-C has some fairly well known memory leaks on shutdown, but no
> known leaks during processing.  Basically, there are a few tables
> that are not cleaned up due to a lack of a reliable automatic
> mechanism to make sure that the code is not reentered after cleanup.
> An explicit Uninitialize call was being considered to free those
> last resources. 

I would be very happy to have these shutdown leaks fixed with an
explicit Uninitialize() call.  This should address both the
"I use Windows and MFC debugging and the leaks bother me" crowd
and the "I don't want to waste time cleaning up on exit()" crowd.

Unfortunately I am in both crowds. :-)

Joseph Chen has some great ideas too.

-- 
Tom Jordahl			tomj@allaire.com
Allaire Corp.			http://www.allaire.com