[AXISCPP-507] Memory leaks in deserialize methods of XSD classes (in src/soap/xsd)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: current (nightly)
• Fix Version/s: 1.5 Final
• Component/s: SOAP
• Assignee: Don Samisa Abeysinghe
• Reporter: Don Samisa Abeysinghe
• Created: 07/Mar/05 13:18
• Updated: 08/Mar/05 18:37
• Resolved: 08/Mar/05 18:37

Description

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 method.
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.

Issue Links

• relates to: AXISCPP-339 Fix trivial memory leaks revealed by profiler tools