etch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Marsh (JIRA)" <>
Subject [jira] [Updated] (ETCH-176) Memory allocated on each service call not released until
Date Mon, 26 Sep 2011 17:21:26 GMT


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:
>             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:


View raw message