[
https://issues.apache.org/jira/browse/ETCH-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Marsh updated ETCH-176:
------------------------------
Attachment: mutex_leak.patch
Note that the mutex lock on g_etch_main_pool_mutex may no longer be necessary.
I have left it in to be on the safe side.
> Memory allocated on each service call not released until
> ---------------------------------------------------------
>
> Key: ETCH-176
> URL: https://issues.apache.org/jira/browse/ETCH-176
> Project: Etch
> Issue Type: Bug
> Components: c-binding
> Environment: Platform independent - seen on 32-but Linux (CentOS 5.6)
> Reporter: Thomas Marsh
> Attachments: mutex_leak.patch
>
>
> Around 32 bytes are leaked on average for every service invocation in the C
> binding. It does not occur for every invocation, but a simple test on the
> helloworld example performing a tight loop over the say_hello method
> demonstrated this leak. The memory consumption is visible in the OS process
> monitor, and was verified using valgrind on Linux.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
