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/09/18 23:55:16 UTC

DO NOT REPLY [Bug 3706] New: - internal memory leak in xerces-c1.5.0

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=3706>.
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=3706

internal memory leak in xerces-c1.5.0

           Summary: internal memory leak in xerces-c1.5.0
           Product: Xerces-C++
           Version: 1.5
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: SAX/SAX2
        AssignedTo: xerces-c-dev@xml.apache.org
        ReportedBy: hpan@secant.com


Platform:

Sun Solaris (Sun OS 5.6), source code is compiled by g++ compiler (gcc: version 
2.95.2).

When I parsed many xml files using SAX2 or SAX1 of xerces-c1.5.0, the parser 
threw an unexpected exception. I found the memory leak resulted in the 
exception.

I did the same thing using xerces-c1.4.0 or xerces-c1.3.0, it worked fine. 

Because I used the same code and xml files, only different version of xerces-c 
lib., the memory leak most probabily is from original source code which was 
added from xerces-c1.4.0 to xerces-c1.5.0.

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org