http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2032 *** shadow/2032 Wed Jun 6 10:41:07 2001 --- shadow/2032.tmp.11577 Wed Jun 6 10:41:07 2001 *************** *** 0 **** --- 1,32 ---- + +============================================================================+ + | DOMString Memory Leak | + +----------------------------------------------------------------------------+ + | Bug #: 2032 Product: Xerces-C | + | Status: NEW Version: 1.4 | + | Resolution: Platform: PC | + | Severity: Critical OS/Version: Windows NT/2K | + | Priority: Other Component: DOM | + +----------------------------------------------------------------------------+ + | Assigned To: [EMAIL PROTECTED] | + | Reported By: [EMAIL PROTECTED] | + | CC list: Cc: | + +----------------------------------------------------------------------------+ + | URL: | + +============================================================================+ + | DESCRIPTION | + To follow the Bug#: 1699 + + The leak also happen in Debug. + So I'm not sure it is only the optimixation flag. + + Just need instantiate a DOMParser and call DOMParser::parse() a couple of time + in a loop to get the leak. + ex: + { + DOMParser myParser; + myParser.parse( myInputBuffer ); + } + + + it seems that DOMString::gLiveStringHandleCount never get down to zero + so no memory is ever freed. \ No newline at end of file --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
