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/06/06 19:41:07 UTC
[Bug 2032] New: - DOMString Memory Leak
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: xerces-c-dev@xml.apache.org |
+ | Reported By: michel.drapeau@ixiasoft.com |
+ | 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: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org