[
http://issues.apache.org/jira/browse/AXISCPP-390?page=comments#action_57769 ]
Samisa Abeysinghe commented on AXISCPP-390:
-------------------------------------------
Here is a sample code segment of the generated code. Note that pSoapFault is
passed to the Calculator_AxisClientException constructor. And
Calculator_AxisClientException class does not clean up this pointer.
catch(AxisException& e)
{
int iExceptionCode = e.getExceptionCode();
if(AXISC_NODE_VALUE_MISMATCH_EXCEPTION != iExceptionCode)
{
throw Calculator_AxisClientException(e.what());
}
=> ISoapFault* pSoapFault = (ISoapFault*)
m_pCall->checkFault("Fault","http://localhost/axis/Calculator"; );
if(pSoapFault)
{
m_pCall->unInitialize();
throw Calculator_AxisClientException(pSoapFault);
}
else throw;
}
> Memory leaks in case of SOAPFault
> ---------------------------------
>
> Key: AXISCPP-390
> URL: http://issues.apache.org/jira/browse/AXISCPP-390
> Project: Axis-C++
> Type: Bug
> Components: Basic Architecture
> Versions: 1.4 Final
> Environment: All platforms
> Reporter: Samisa Abeysinghe
> Fix For: 1.5 Alpha
>
> The pointer returned to the SOAPFault object is never deallocated in the
> generated code in case of a fault. The pointer is returned by
> Call::checkFault() method and memory is allocated by
> SoapDeSerializer::checkForFault()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.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
