Memory leaks in XSD type classes - should define destructor to clean

• Key: AXISCPP-384
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Major
• Assignee: Samisa Abeysinghe
• Reporter: Samisa Abeysinghe
• Component/s: Basic Architecture
• Affects Version/s: current (nightly)
• Fix Version/s: current (nightly)

Description

There are numerous memory leaks in the classes in ws-axis\c\src\soap\xsd. This was revealed by purifier tools.

Especially the memory allocated inside serialize method is never deallocated.

Comments

[Samisa Abeysinghe]

Additionally, have to use memory allocation best practices in allocating/deallocating memory.

[Samisa Abeysinghe]

Fixed HexBinary class

[Samisa Abeysinghe]

Adrian, I assigned you as per your request. Thanks.

[Johan Fischer]

Isn't it related to AXISCPP-359 ?

Cheers.

[Samisa Abeysinghe]

AXISCPP-359 is not the same but is related.
Worth having a look into that as well.

AXISCPP-359 looks important for continuously running applications

[Adrian Dick]

All existing XSD objects have now had the suggested changes made, to prevent memory leaks.
I shall ensure the remaining XSD objects will be implemented to incorporate these suggestions.

[Samisa Abeysinghe]

There seem to be some few more hidden leaks. I will try and fix those

[Samisa Abeysinghe]

Fixed some more leaks in Int, Integer, Float, Decimal, DateTime, Base64Binary and HexBinary classes

[Samisa Abeysinghe]

Many leaks related to xsd types were fixed with the help from Adrian