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/07/17 09:16:27 UTC
[Bug 2649] New: - Huge memory leaks in Xerces
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2649
*** shadow/2649 Tue Jul 17 00:16:27 2001
--- shadow/2649.tmp.20536 Tue Jul 17 00:16:27 2001
***************
*** 0 ****
--- 1,26 ----
+ +============================================================================+
+ | Huge memory leaks in Xerces |
+ +----------------------------------------------------------------------------+
+ | Bug #: 2649 Product: Xerces-C++ |
+ | Status: NEW Version: 1.5 |
+ | Resolution: Platform: PC |
+ | Severity: Critical OS/Version: Windows NT/2K |
+ | Priority: Other Component: Non-Validating Parser |
+ +----------------------------------------------------------------------------+
+ | Assigned To: xerces-c-dev@xml.apache.org |
+ | Reported By: guy.vinograd@ecitele.com |
+ | CC list: Cc: |
+ +----------------------------------------------------------------------------+
+ | URL: |
+ +============================================================================+
+ | DESCRIPTION |
+ The problem is memory leaks that are steadily growing. Scenario:
+ I took DomPrint sample project and added a loop around the section starting at
+ DOMParser *parser = new DOMParser;
+ and ending at
+ delete parser;
+
+ Then by looking at the memory consumption of domprint.exe (using task manager)
+ i saw that the memory is growing rapidly.
+
+ In version 1.4 the memory is stable.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org