[asterisk-bugs] [JIRA] (ASTERISK-26078) core: Memory leak in logging

[Richard Mudgett (JIRA)]

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

Richard Mudgett closed ASTERISK-26078.
--------------------------------------

    Resolution: Fixed

> core: Memory leak in logging
> ----------------------------
>
>                 Key: ASTERISK-26078
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26078
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Logging
>    Affects Versions: 13.8.0, 13.9.1
>         Environment: Debian 8 amd64
>            Reporter: Etienne Lessard
>            Assignee: Richard Mudgett
>         Attachments: jira_asterisk_26078_v13.patch, mmlog, mmsummary1, mmsummary2, valgrind.txt
>
>
> There seems to be a new memory leak since Asterisk 13.8 or 13.9.
> Running a simple call center scenario with sipp (a new call into a queue every few seconds, that is answered by a queue member, etc), I'm seeing asterisk memory usage grow noticeably (a little bit less than 100 MB/hour).
> Looking at a diff from two "memory show summary" commands taken 30 minutes apart, it looks like the leak comes from logger.c / stringfields.c. I've attached the output of two "memory show summary".
> I've also attached the mmlog file, but I doubt this will be useful since it's mostly empty (guess I've done something wrong).
> I'm already aware of ASTERISK-25262, but this is not it: I've explicitly disabled the CEL in my current tests. I've also seen ASTERISK-25905, but this is not it (I've also try manually running malloc_trim, it gave nothing). Maybe it's similar to ASTERISK-26020, but there's not much info in that ticket.
> Thank you



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