[ http://nagoya.apache.org/jira/browse/XERCESC-1307?page=comments#action_56367 ] Mariusz Popiolek commented on XERCESC-1307: -------------------------------------------
I've checked your fix and now everything is fine. Thanks > 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
