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 "Alberto Massari (JIRA)" <xe...@xml.apache.org> on 2004/12/08 13:13:14 UTC

[jira] Closed: (XERCESC-1307) memory leak in xercesc::XMLUri::operator =

     [ http://nagoya.apache.org/jira/browse/XERCESC-1307?page=history ]
     
Alberto Massari closed XERCESC-1307:
------------------------------------


> memory leak in xercesc::XMLUri::operator =
> ------------------------------------------
>
>          Key: XERCESC-1307
>          URL: http://nagoya.apache.org/jira/browse/XERCESC-1307
>      Project: Xerces-C++
>         Type: Bug
>   Components: Utilities
>     Versions: 2.5.0
>  Environment: WindowsXP, Visual Studio 6.0 SP6
>     Reporter: Mariusz Popiolek
>     Priority: Minor

>
> I'm using Xerces 2.5 and I think that there is a memory leakage in 
> xercesc::XMLUri::operator = . If this function is being used with already 
> initialized object, previously allocated memory is not deallocated (that's 
> what shows Visual Studio after terminating program and after brief check 
> of xerces source code I think that this time VS memory leakage report is 
> true).  I also tried to invoke xercesc::XMLUri::operator = in loop and I 
> can see that memory usage of process is growing. 
> Is there any workaround? I tried calling destructor explicitly  but in 
> some cases program crashes when destructor is called implicitly. I would 
> like to avoid calling setXXX(getXXX) multiple times.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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