[asterisk-bugs] [JIRA] (ASTERISK-28523) Asterisk 16.5.0 Memory leak

[Asterisk Team (JIRA)]

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

Asterisk Team updated ASTERISK-28523:
-------------------------------------

    Target Release Version/s: 17.0.0

> Asterisk 16.5.0 Memory leak
> ---------------------------
>
>                 Key: ASTERISK-28523
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28523
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 16.5.0
>         Environment: Ubuntu 16.04.6 LTS / AWS C5.* instance
>            Reporter: Cyril Ramière
>            Assignee: Kevin Harwell
>              Labels: pjsip, webrtc
>      Target Release: 17.0.0
>
>         Attachments: ast_ram_24h.PNG, ast_ram_up.PNG, ast_sorcery_cache_endpoints_2000vs500.PNG, config.zip, endpoints.1000.sql, endpoints.2000.sql, extconfig.conf, extensions.conf, invite.csv, invite_recv.xml, invite.xml, leak_caching.txt, leak_without_caching.txt, memory_show_allocations_24h.zip, memory_show_allocations.zip, memory_show_summary_24h.txt, memory_show_summary.txt, modules.conf, pjsip.conf, res_odbc.conf, sorcery.conf
>
>
> Hello everyone,
> I noticed that our asterisk are consuming big amounts of ram (could be more than 1.6Gb after some days/weeks depending on server load).
> We are using asterisk in realtime mode for all of our calls with MySQL (res_mysql).
> Everything is handled through the ARI interface (dialplan passes to Stasis) connected to our application.
> I attached the full configuration of our asterisk server, I just replaced sensitive information to not expose our passwords/endpoints.
> I'm currently running an instance with MALLOC_DEBUG & no optimize, it's been couple hours since I started my test and it is taking almost 300Mb for now (it will continue to grow).
> Here is the result of commands memory show.
> Best regards.



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