Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 1309 invoked from network); 28 Jun 2005 02:47:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 28 Jun 2005 02:47:15 -0000 Received: (qmail 28637 invoked by uid 500); 28 Jun 2005 02:47:14 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 28622 invoked by uid 500); 28 Jun 2005 02:47:14 -0000 Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C Developers List" Reply-To: "Apache AXIS C Developers List" Delivered-To: mailing list axis-c-dev@ws.apache.org Received: (qmail 28609 invoked by uid 99); 28 Jun 2005 02:47:14 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Jun 2005 19:47:13 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [12.40.51.197] (HELO mailhost.virtusa.com) (12.40.51.197) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Jun 2005 19:47:13 -0700 Received: from cs-mailsvr.Virtusa.com ([10.2.1.11]unverified) by mailhost.virtusa.com with InterScan Messaging Security Suite; Mon, 27 Jun 2005 22:45:29 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C57B8B.AB8394C8" Subject: RE: Memory leaks Date: Tue, 28 Jun 2005 08:46:53 +0600 Message-ID: <403DD48EAE182940B89ECEAFE03F969005B2236E@cs-mailsvr.Virtusa.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Memory leaks Thread-Index: AcV7YB9P3MiYhImeTv+ZoqdLkQOqYQAKsb9Q From: "Samisa Abeysinghe" To: "Apache AXIS C Developers List" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------_=_NextPart_001_01C57B8B.AB8394C8 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Carsten, I too was having a look into the memory leaks last Friday and noticed considerable amounts of memory leaks.=20 I was using the base sample and noticed as the memory management model has changed, there were many leaks in the main program code (that is user written code). Not sure if your generated code level fixes that you have done would look after those as well. =20 Please check in the code, and then I can have a secondary look. Thanks, Samisa... =20 -----Original Message----- From: Carsten Blecken [mailto:cblecken@macrovision.com]=20 Sent: Tuesday, June 28, 2005 3:35 AM To: axis-c-dev@ws.apache.org Subject: Memory leaks =20 Hi,=20 as we all know there are memory leaks in the current code base(AXISCPP-674).=20 I had to manually change the stubs in order to get a memory leak free application.=20 I would like to add the memory changes I needed to the WSDL stub=20 generator code base (doc-lit, C++).=20 The approach for memory deallocation suggested in various places in the=20 code (in comments) is to free the memory of primitive types right away in the=20 stub and to free pointer types and complex type in the destructor (after the client=20 has used them). This is the approach I followed.=20 If I don't hear anything to the contrary I'll checkin the fixes in the next couple of days.=20 Thanks,=20 Carsten=20 =20 =20 ------_=_NextPart_001_01C57B8B.AB8394C8 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Memory leaks

Hi Carsten,

        = ;    I too was having a look into the memory leaks last Friday and noticed considerable amounts of memory leaks.

        = ;    I was using the base sample and noticed as the memory management model has changed, there were many leaks in the main program code (that is user = written code).

        = ;    Not sure if your generated code level fixes that you have done would look = after those as well.

 

        = ;    Please check in the code, and then I can have a secondary = look.

Thanks,

=

Samisa…

 

-----Original = Message-----
From: Carsten Blecken [mailto:cblecken@macrovision.com]
Sent: Tuesday, June 28, = 2005 3:35 AM
To: = axis-c-dev@ws.apache.org
Subject: Memory = leaks

 

Hi,

as we all know there are memory leaks in the = current code base(AXISCPP-674).
 I had to manually change the stubs in order to get a memory leak free application.
I would like to add the memory changes I needed to the WSDL stub =
generator code base (doc-lit, C++).

The approach for memory deallocation suggested = in various places in the
code (in comments) is to free the memory of primitive types right away in the =
stub and to free pointer types and complex type in the destructor (after the = client
has used them). This is the approach I followed. =

If I don't hear anything to the contrary I'll = checkin the fixes in the next couple of days.

Thanks,

Carsten

 

 

------_=_NextPart_001_01C57B8B.AB8394C8--