axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chinthana Danapala (JIRA)" <>
Subject [jira] Updated: (AXISCPP-342) There are too many leaks and possibilities for leaks in Param class and ParamValue class
Date Mon, 19 Sep 2005 09:43:54 GMT
     [ ]

Chinthana Danapala updated AXISCPP-342:

    Attachment: ParamCppDiff

Hi all,

After reporting this bug there are so many changes have done for this Param.cpp class.
I have attached the diff file current code and version has used to report the bug. I feel
most of the memory problems must be overcome with this changes. There was a patch attached
to overcome memory leaks and I have gone through it and I found that most of changes are depend
on old code which has removed in latest version.  

Anyone would be able to check latest code memory lakes and report would be great. 

> There are too many leaks and possibilities for leaks in Param class and ParamValue class
> ----------------------------------------------------------------------------------------
>          Key: AXISCPP-342
>          URL:
>      Project: Axis-C++
>         Type: Bug
>   Components: Serialization
>     Versions: 1.4 Final
>  Environment: All platforms
>     Reporter: Samisa Abeysinghe
>     Assignee: Chinthana Danapala
>      Fix For: 1.6 Alpha
>  Attachments: Param.DIFF, ParamCppDiff
> There are too many leaks in the class Param and the associated class ParamValue.
> As these are not documented (specially the couplings/dependancies) it is time consuming
to fix them.
> Cleaning up members of ParamValue class is done by Param class - this is *VERY* bad -
as it is difficult to track what has been release and what not.
> As a solution, need to make the class ParamValue a class of its own with destructor,
constructor, copy constructor and assignment operator.
> Param class should need only worry about its own members.
> These leaks become apparent when there are exceptions with complex detail objects - I
used tests/client/fault_mapping to track those.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message