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

[Bill Brigden (JIRA)]

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

Bill Brigden commented on ASTERISK-27281:
-----------------------------------------

FYI - this can now be marked as resolved+fixed - it was fixed by the recent commit reported on case ASTERISK-27679 (which had linked here):

{noformat}
* res_pjsip: Endpoint destruction does not free DTLS configuration
	  ASTERISK-27679 #close
	  Reported by: Mak Dee
{noformat}

> 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
>            Assignee: Unassigned
>         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)