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

List:       axis-c-dev
Subject:    [jira] [Commented] (RAMPARTC-153) [PATCH] Memory leak in in_handler
From:       "Garrett Holmstrom (JIRA)" <jira () apache ! org>
Date:       2011-06-02 16:41:52
Message-ID: 903591524.63219.1307032912639.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/RAMPARTC-153?page=com.atlassian.jira.plugi \
n.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042857#comment-13042857 ] \


Garrett Holmstrom commented on RAMPARTC-153:
--------------------------------------------

David, are you able to point me to some code that triggers such a segfault?  That \
might help me work out a better solution.

> [PATCH] Memory leak in in_handler
> ---------------------------------
> 
> Key: RAMPARTC-153
> URL: https://issues.apache.org/jira/browse/RAMPARTC-153
> Project: Rampart/C
> Issue Type: Bug
> Components: Rampart-core
> Affects Versions: 1.3.0
> Environment: Linux (all distributions)
> Reporter: Garrett Holmstrom
> Assignee: Malinda Kaushalye Kapuruge
> Labels: patch
> Attachments: rampart-trunk-memleak.patch
> 
> 
> The rampart_in_handler_invoke function leaks memory every time it succeeds because \
> it fails to free rampart_context before returning.  The attached patch makes it \
> call rampart_context_free before returning. Ubuntu has been carrying a patch for \
> this for some time, so it would be nice to get it upstream if possible.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: c-dev-help@axis.apache.org


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