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 bu...@apache.org on 2001/10/22 12:13:20 UTC
DO NOT REPLY [Bug 4325] New: -
Memory Leaks in the basic parser operation
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4325>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4325
Memory Leaks in the basic parser operation
Summary: Memory Leaks in the basic parser operation
Product: Xerces-C++
Version: 1.5.1
Platform: PC
OS/Version: Linux
Status: NEW
Severity: Critical
Priority: Other
Component: SAX/SAX2
AssignedTo: xerces-c-dev@xml.apache.org
ReportedBy: akseli.karpo@luukku.com
Dear all:
I've got a server-like application (which is supposed to be running forever) and
within this application I wish to utilise the SAXparser. It turned out that the
parser has memory leaks. It reserves several hundreds of bytes on each
parse-operation.
I've got linux 2.4.9, gcc 2.96.
I'm using the library 'libxerces-c1_5_1.so' that comes with the tar.
I've also learned that one can call XMLPlatformUtilities::Initialize() only once
within the same process.
The application code snippet below:
XxxxReturn_t XxxxXMLParser_c::Parse( const char *bufferi)
{
try
{
MemBufInputSource* memBufIS = new MemBufInputSource ( (const XMLByte*)bufferi,
strlen(bufferi),
"mBufId",
false );
parser = new SAXParser();
parser->parse( *memBufIS );
delete memBufIS;
delete parser;
}
catch (const XMLException& toCatch)
{
return XXXX_RETURN_ERROR;
}
return XXXX_RETURN_OK;
}
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org