[asterisk-bugs] [JIRA] (ASTERISK-22833) channel: Channel reference leak
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Thu Jan 9 17:41:03 CST 2014
[ https://issues.asterisk.org/jira/browse/ASTERISK-22833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rusty Newton updated ASTERISK-22833:
------------------------------------
Assignee: Mitch Rodrigues (was: Rusty Newton)
Status: Waiting for Feedback (was: Triage)
@Mitch,
I had a couple developers look at the refcounter output, and it appears it is all benign, some of it from only ref debugging chan_sip and not all modules.
At this point we are unable to reproduce the issue and therefore can't move forward with diagnosis.
Would you be able to provide a full /tmp/refs file from a system where the issue occurs (and where ref count debugging is enabled for all Asterisk modules)? If possible, you'll probably want to set that up on a non-production system.
Otherwise we'll need more specific instructions on exactly how to reproduce the issue, as what we have so far didn't work.
> channel: Channel reference leak
> -------------------------------
>
> Key: ASTERISK-22833
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-22833
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Core/Channels
> Affects Versions: 11.5.1, 11.6.0
> Environment: centos
> Reporter: Mitch Rodrigues
> Assignee: Mitch Rodrigues
> Severity: Critical
> Attachments: extensions.txt, fd_after_1000.txt, fd_at_idle.txt, refcounter_output.txt, refs.txt, sip.txt
>
>
> fd pipes linger from channel internals after call has been terminated. Seems to to also leave around alot of anon_inodes when doing lsof
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list