You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by Dean Roddey <dr...@charmedquark.com> on 2002/07/25 23:14:03 UTC
RE: memory leak in xerces c 2.0.0??
Unless I'm missing something, it's the usual thing where the tool is too
stupid to realize that its dealing with C++, and that the buffer
allocated in the constructor is later going to be freed in the
destructor. Don't trust those tools unless you look yourself and see
what's going on.
-------------------------------------
Dean Roddey
The Charmed Quark Controller
droddey@charmedquark.com
www.charmedquark.com
-----Original Message-----
From: eko@hns.com [mailto:eko@hns.com]
Sent: Thursday, July 25, 2002 2:14 PM
To: xerces-c-dev@xml.apache.org
Subject: memory leak in xerces c 2.0.0??
Hi,
I run the xerces c 2.0.0 under purify, and it show that it got memory
leak in
:
MLK: 612352 bytes leaked in 299 blocks
* This memory was allocated from:
malloc [rtlib.o]
c2n6Fi_Pv___1 [libCrun.so.1]
void*operator new(unsigned) [rtlib.o]
void*operator new[](unsigned) [rtlib.o]
XMLBuffer::XMLBuffer(int) [libxerces-c.so.20.0]
DOMDocumentTypeImpl::DOMDocumentTypeImpl(DOMDocument*,const
unsigned
short*,const unsigned short*,const unsigned short*,bool) [
DOMDocumentTypeImpl.cpp]
DOMDocumentType*DOMDocumentImpl::createDocumentType(const
unsigned
short*,const unsigned short*,const unsigned short*) [DOMDocu
mentImpl.cpp:299]
void AbstractDOMParser::doctypeDecl(const DTDElementDecl&,const
unsigned short*const,const unsigned short*const,const bool) [Ab
stractDOMParser.cpp:1007]
void XMLScanner::scanDocTypeDecl() [XMLScanner.cpp:2460]
void XMLScanner::scanProlog() [XMLScanner.cpp:2256]
void XMLScanner::scanDocument(const InputSource&)
[XMLScanner.cpp:446]
void AbstractDOMParser::parse(const InputSource&)
[AbstractDOMParser.cpp:339]
I run the same xml file using the same piece of code with a stable build
from
tar file
xerces-c-src_2002-07-14.tar, I don't see any memory leak related to the
parser
.
Do you think this is a real memory leak? If yes, Can it be fix soon??
Thanks !
Eva
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org