axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Updated: (AXISCPP-61) STL map memory leaks - patch
Date Fri, 07 May 2004 07:35:56 GMT
The following issue has been updated:

    Updater: Susantha Kumara (mailto:susantha@opensource.lk)
       Date: Fri, 7 May 2004 12:35 AM
    Changes:
             Attachment changed from SLT map patches.rar
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/AXISCPP-61?page=history

---------------------------------------------------------------------
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: Fri, 7 May 2004 12:35 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


Mime
View raw message