axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe (JIRA)" <>
Subject [jira] Commented: (AXISCPP-507) Memory leaks in deserialize methods of XSD classes (in src/soap/xsd)
Date Tue, 08 Mar 2005 07:41:52 GMT
     [ ]
Samisa Abeysinghe commented on AXISCPP-507:

OK I figured out the other problems - there seem to be some classes calling others in deserailizing
- e.g. Int -> Long -> Integer

> Memory leaks in deserialize methods of XSD classes (in src/soap/xsd)
> --------------------------------------------------------------------
>          Key: AXISCPP-507
>          URL:
>      Project: Axis-C++
>         Type: Bug
>   Components: SOAP
>     Versions: current (nightly)
>     Reporter: Samisa Abeysinghe
>     Assignee: Samisa Abeysinghe
>      Fix For: 1.5 Final
>  Attachments: Document style.txt, RPC style.txt
> Deserialize method returns a pointer that is never deleted. The generated code, dereferances
the pointer and returns values to the Stub.
> Hence, the generated code should take care of the clearance of memeory.
> I tried to release this  memeory in the destructor of the XSD class, but then by the
time the generated code tries to access the value, the pointer is no more. This leaves the
only option of deleting the memory returned in the generated code where it invokes the respective
> Alternatively, we can make the XSD class manage its own memory and let the code accessing
the memory make a deep copy of the returned pointer (that is generated code)
> Whateve the fix would be, it needs changes to code generator.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message