[asterisk-bugs] [JIRA] (ASTERISK-23616) Big memory leak in logger.c

Corey Farrell (JIRA) noreply at issues.asterisk.org
Mon Apr 14 10:06:19 CDT 2014


    [ https://issues.asterisk.org/jira/browse/ASTERISK-23616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217303#comment-217303 ] 

Corey Farrell commented on ASTERISK-23616:
------------------------------------------

I realize the code at the end is currently dead and plan to eventually submit a patch to exit autoservice at asterisk shutdown.  However on the other point, {{unique_callid_cleanup}} is used to clean the thread local storage, and it does release the reference if one exists.

> Big memory leak in logger.c
> ---------------------------
>
>                 Key: ASTERISK-23616
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23616
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Logging
>    Affects Versions: 11.8.0
>            Reporter: ibercom
>            Assignee: ibercom
>         Attachments: autoservice-callid-leak.patch, autoservice-callid-leak-v2.patch, callid-refleaks.txt, jira_asterisk_23616_v11_autoservice_leak.patch, memory2.tar.gz, memory.tar.gz, refs2.gz, refs.gz
>
>
> Once under a non-trivial load, Asterisk 11 produces a high volume of memory leak in logger.c
> After processing 40039 calls "memory show summary" shows 176983 allocations:
> 560830 bytes in      13817 allocations in file logger.c
> It grows and grows.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list