Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 70244 invoked from network); 8 Mar 2005 07:30:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 8 Mar 2005 07:30:58 -0000 Received: (qmail 30158 invoked by uid 500); 8 Mar 2005 07:30:57 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 30048 invoked by uid 500); 8 Mar 2005 07:30:57 -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 29877 invoked by uid 99); 8 Mar 2005 07:30:56 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from ajax-1.apache.org (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 07 Mar 2005 23:30:54 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (8.12.11/8.12.11) with ESMTP id j287Uqqx027804 for ; Tue, 8 Mar 2005 08:30:52 +0100 Message-ID: <1078250841.1110267052342.JavaMail.jira@ajax.apache.org> Date: Tue, 8 Mar 2005 08:30:52 +0100 (CET) From: "Samisa Abeysinghe (JIRA)" To: axis-c-dev@ws.apache.org Subject: [jira] Commented: (AXISCPP-507) Memory leaks in deserialize methods of XSD classes (in src/soap/xsd) In-Reply-To: <227483935.1110169492265.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/AXISCPP-507?page=comments#action_60412 ] Samisa Abeysinghe commented on AXISCPP-507: ------------------------------------------- Hi Chinthana, I had a look at the RPC style solution you provided here. It solves the problem partially - but not completely :( > Memory leaks in deserialize methods of XSD classes (in src/soap/xsd) > -------------------------------------------------------------------- > > Key: AXISCPP-507 > URL: http://issues.apache.org/jira/browse/AXISCPP-507 > Project: Axis-C++ > Type: Bug > Components: SOAP > Versions: current (nightly) > Reporter: Samisa Abeysinghe > Assignee: Samisa Abeysinghe > Fix For: 1.5 Final > Attachments: Document style.txt, RPC style.txt > > Deserialize method returns a pointer that is never deleted. The generated code, dereferances the pointer and returns values to the Stub. > Hence, the generated code should take care of the clearance of memeory. > I tried to release this memeory in the destructor of the XSD class, but then by the time the generated code tries to access the value, the pointer is no more. This leaves the only option of deleting the memory returned in the generated code where it invokes the respective method. > Alternatively, we can make the XSD class manage its own memory and let the code accessing the memory make a deep copy of the returned pointer (that is generated code) > Whateve the fix would be, it needs changes to code generator. -- 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