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

[Richard Mudgett (JIRA)]

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

Richard Mudgett commented on ASTERISK-23616:
--------------------------------------------

Corey, the code at the end of the procedure is really dead code since the autoservice thread never exits.  However, the thread exit will not release the callid reference held by the thread local storage since it only knows how to release the storage itself.

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