[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:all-tabpanel ]

Richard Mudgett updated ASTERISK-23616:
---------------------------------------

    Attachment: jira_asterisk_23616_v11_autoservice_leak.patch

Good job finding that ref leak Corey.

After looking at your patch [^autoservice-callid-leak.patch], I think this patch [^jira_asterisk_23616_v11_autoservice_leak.patch] is better in that it won't spam the debug logs when TEST_FRAMEWORK in enabled.  IIRC, not spamming the debug log is why ast_callid_threadassoc_change() was created.

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