[asterisk-bugs] [JIRA] (ASTERISK-23616) Big memory leak in logger.c
Corey Farrell (JIRA)
noreply at issues.asterisk.org
Thu Apr 10 14:12:18 CDT 2014
[ https://issues.asterisk.org/jira/browse/ASTERISK-23616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217221#comment-217221 ]
Corey Farrell commented on ASTERISK-23616:
------------------------------------------
Based on the memalloc inside memory.tar.gz, you are leaking memory allocated by {{ast_create_callid}}. Based on this we need to see /tmp/refs with {{REF_DEBUG}} defined for the whole system. It's unlikely this is an actual leak in the logger. Most likely something else that uses the callid is leaking it's reference.
> 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: memory.tar.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)
More information about the asterisk-bugs
mailing list