[prev in list] [next in list] [prev in thread] [next in thread] 

List:       axis-c-dev
Subject:    [jira] Commented: (AXISCPP-61)  STL map memory leaks - patch
From:       jira () apache ! org
Date:       2004-04-28 10:45:00
Message-ID: 264727450.1083149100601.JavaMail.apache () nagoya
[Download RAW message or body]

The following comment has been added to this issue:

     Author: Sevwandi Abeysinghe
    Created: Wed, 28 Apr 2004 3:43 AM
       Body:
Since rar files are difficult to use in Linux seperate diff files are being attached.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXISCPP-61?page=comments#action_35307

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXISCPP-61

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXISCPP-61
    Summary:  STL map memory leaks - patch
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: Axis-C++
 Components: 
             Performance
   Versions:
             1.1 Final

   Assignee: 
   Reporter: Sevwandi Abeysinghe

    Created: Mon, 26 Apr 2004 1:59 AM
    Updated: Wed, 28 Apr 2004 3:43 AM
Environment: All platforms

Description:
The use of STL map seems to cause memeory leaks (it leaves 
'reachable memory' behind after client terminates)

It is quite possible to do without the STL map in some cases. This is been done  for \
SoapKeywordMapping. (see patch in attached file)

In cases it is difficult to replace maps with arrays (as an exampel when key is a \
string) may have to look for alternatives.  
Is it possible to replace STL map with our own map? (To do this without templates, \
may have to stick to string keys)  
Some memory leaks fixed are fixed in SoapKeywordMapping code. Need to 
call SoapKeywordMapping::uninitialize () from Axis.cpp uninitialize_module() to make \
this effective.





---------------------------------------------------------------------
JIRA INFORMATION:
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


[prev in list] [next in list] [prev in thread] [next in thread]