[asterisk-bugs] [JIRA] (ASTERISK-27281) Increased memory usage when using Sorcery Caching

[Richard Mudgett (JIRA)]

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

Richard Mudgett commented on ASTERISK-27281:
--------------------------------------------

These wiki pages talk about what is needed to help find memory leaks:
https://wiki.asterisk.org/wiki/display/AST/Memory+Leak+Debugging
https://wiki.asterisk.org/wiki/display/AST/MALLOC_DEBUG+Compiler+Flag

You may want to upgrade to the latest v13 release to see if the memory leak has already been fixed.

> Increased memory usage when using Sorcery Caching
> -------------------------------------------------
>
>                 Key: ASTERISK-27281
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27281
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.14.0
>         Environment: Debian 8.7
>            Reporter: Bill Brigden
>         Attachments: mem2.PNG
>
>
> When using Sorery enabled with config like:
> {noformat}
> [res_pjsip]
> endpoint/cache=memory_cache,object_lifetime_stale=600,object_lifetime_maximum=1800,expire_on_reload=yes,maximum_objects=500
> endpoint=realtime,ps_endpoints
> endpoint=config,pjsip.conf,criteria=type=endpoint
> auth/cache=memory_cache,object_lifetime_stale=600,object_lifetime_maximum=1800,expire_on_reload=yes,maximum_objects=500
> auth=realtime,ps_auths
> aor/cache=memory_cache,object_lifetime_stale=600,object_lifetime_maximum=1800,expire_on_reload=yes,maximum_objects=500
> aor=realtime,ps_aors
> aor=config,pjsip.conf,criteria=type=aor
> domain_alias=realtime,ps_domain_aliases
> contact=realtime,ps_contacts
> {noformat}
> I've seen increasing memory usage until the server runs out of memory (and swap). If I comment out the "/cache" lines - memory usage stays relatively stable.
> Happy to collate logs / info however would appreciate guidance on what is required to diagnose the cause of unreleased memory.
> I'll upload a screenshot of my collectd graphing post-creation



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