[asterisk-bugs] [JIRA] Commented: (ASTERISK-20335) Crash in ast_cel_report_event
aragon (JIRA)
noreply at issues.asterisk.org
Fri Aug 31 08:34:08 CDT 2012
[ https://issues.asterisk.org/jira/browse/ASTERISK-20335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196483#comment-196483 ]
aragon commented on ASTERISK-20335:
-----------------------------------
I went through all of the Asterisk 1.8.16rc1 and svn change logs and recent changes were made to cel.
Therefore I wonder if this is a regression...
2012-07-18 19:12 +0000 [r370183-370205] Kevin P. Fleming <kpfleming at digium.com>
* main/cel.c: Resolve severe memory leak in CEL logging modules. A
customer reported a significant memory leak using Asterisk 1.8.
They have tracked it down to
ast_cel_fabricate_channel_from_event() in main/cel.c, which is
called by both in-tree CEL logging modules (cel_custom.c and
cel_sqlite3_custom.c) for each and every CEL event that they log.
The cause was an incorrect assumption about how data attached to
an ast_channel would be handled when the channel is destroyed;
the data is now stored in a datastore attached to the channel,
which is destroyed along with the channel at the proper time.
(closes issue AST-916) Review:
https://reviewboard.asterisk.org/r/2053/
> Crash in ast_cel_report_event
> -----------------------------
>
> Key: ASTERISK-20335
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-20335
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_local
> Affects Versions: 1.8.16.0
> Environment: Centos server 5.8x64, 8 core CPU, 8GB RAM
> Reporter: aragon
> Assignee: aragon
> Severity: Critical
> Attachments: AST18-core-verbose.txt, asterisk.txt, core show channels.txt, optimized backtrace.txt, SIP show channels.txt, verbose CLI sip set debug on.txt
>
>
> On a pretty busy system we get deadlocks and crashes daily since installing Asterisk 1.8.16rc1
> Upgraded from 1.8.12 because we were having problems with leaking bye's fixed in ASTERISK-19455
> We were able to collect verbose CLI, core show channels, sip show channels, and Asterisk CLI with sip set debug on.
> Also back traced a core dump file but this is an optimized build since we could not run non-optimized in this environment.
> Including the back trace anyway since it might help diagnose the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list