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

[Corey Farrell (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-23616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Corey Farrell updated ASTERISK-23616:
-------------------------------------

    Attachment: autoservice-callid-leak.patch

I believe you are experiencing a leak from autoservice.  I was unable to match the following ref's to unref's:
{noformat}
   0x25b3450 +1   channel_internal_api.c:869:ast_channel_callid () [@2]
   0x25b3450 +1   logger.c:1368:ast_callid_threadassoc_change () [@3]
{noformat}

I searched the asterisk source, and found autoservice is the only caller of {{ast_read_threadstorage_callid}}.

[~ibercom]: Please try autoservice-callid-leak.patch, let us know if this solves your problem (either fully or partially).

> 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, callid-refleaks.txt, 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)