You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-c-dev@ws.apache.org by "Manjula Peiris (JIRA)" <ji...@apache.org> on 2009/01/22 18:34:00 UTC
[jira] Commented: (RAMPARTC-131) Memory leak after policy creation
[ https://issues.apache.org/jira/browse/RAMPARTC-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666225#action_12666225 ]
Manjula Peiris commented on RAMPARTC-131:
-----------------------------------------
Can't send the backtraces of the memory leaks , created from a tool like purify, valgrind or any other ?
> Memory leak after policy creation
> ---------------------------------
>
> Key: RAMPARTC-131
> URL: https://issues.apache.org/jira/browse/RAMPARTC-131
> Project: Rampart/C
> Issue Type: Bug
> Components: Security policy
> Affects Versions: 1.2.0
> Environment: Axis2/c 1.5.0
> Rampart/c 1.2.0
> Visual Studio 9
> Reporter: M. Wiesner
> Assignee: Malinda Kaushalye Kapuruge
> Attachments: axis2.xml, memoryleakdump2, policy.xml
>
>
> After creating a policy for a service client with
> policy = neethi_util_create_policy_from_file(env, policyFile);
> we detected memory leaks. (approach: http://msdn.microsoft.com/en-us/library/e5ewb1h3(VS.80).aspx)
> Running a loop of creating service clients showed a constant increase of memory usage.
> The same happens when using one of the Rampart examples (samples\client\sec_echo).
> Attachements:
> - memory dump
> - policy.xml
> - axis2.xml
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.