Note that my little experience with xerces showed it hoggs memory rather than leak it (arguably a matter of semantics, since xerces manages memory internally). Back then, I traced my problem to large-scale use of getElementsByTagName(). (BTW: This is a known issue since xerces-c 2.5: (http://issues.apache.org/jira/browse/XERCESC-1465). HTH, Amit
> -----Original Message----- > From: Sousa, Rafael (ext) [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 21, 2006 21:54 > To: [email protected] > Subject: Memory leaks in Xerces-C++ > > > Hi all! > > Have any memory leaks been detected and corrected in > libxerces-c lately? > > I've been using a compilation I did for Solaris last November > 2005, and now I'm suspecting that I may have memory leaks in it. > > On your site, I can see that Xerces is still in version > 2.7.0. Has it not suffered any changes since? > > Thanks > > Rafael > >
