[jira] Resolved: (XERCESC-534) Memory leak in DOMParser

["Alberto Massari (JIRA)" <xe...@xml.apache.org>]

     [ https://issues.apache.org/jira/browse/XERCESC-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alberto Massari resolved XERCESC-534.
-------------------------------------

    Resolution: Won't Fix
      Assignee:     (was: Xerces-C Developers Mailing List)

DOMParser has been deprecated in v. 2.0

> Memory leak in DOMParser
> ------------------------
>
>                 Key: XERCESC-534
>                 URL: https://issues.apache.org/jira/browse/XERCESC-534
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: Non-Validating Parser
>    Affects Versions: 1.7.0
>         Environment: Operating System: Windows NT/2K
> Platform: PC
>            Reporter: Derek
>
> I have found a memory leak in the DOMParser class. The parser method seem to 
> leak memory every time I call it. I compiled the one of the samples (MemParse) 
> and it also seem to loose memory. 
> I parse a xml stream from memory using the MemBufInputSource class. The leak 
> size depends on the size of the xml stream.
> I have written a server type application that resolves xml requests from the 
> web. If the application runs through a few request, I loose a significaqnt 
> amount of memory. Is there something that I do not initialise or something 
> thast I might be doing wrong?
> Code:
> XMLPlatformUtils::Initialize();
> DOMParser *p = new DOMParser();
> MemBufInputSource source(...);
> try{
>    p->parse(source); // This statement seem to loose memory.
> }
> catch{ ... }
> delete p;
> XMLPlatformUtils::Terminate();
> regards
> Derek

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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