[
https://issues.apache.org/jira/browse/RAMPARTC-153?page=com.atlassian.jira.plugin.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: [email protected]
For additional commands, e-mail: [email protected]
