[asterisk-bugs] [JIRA] (ASTERISK-24784) Asterisk v13.2.0 + chan_sip + leaks pipes

[Joshua Colp (JIRA)]

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

Joshua Colp commented on ASTERISK-24784:
----------------------------------------

This is a duplicate of ASTERISK-24768. In the case of Certified Asterisk the res_timing_pthread module is not enabled by default, so it would not be used.

> Asterisk v13.2.0 + chan_sip + leaks pipes
> -----------------------------------------
>
>                 Key: ASTERISK-24784
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24784
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General, Core/Channels
>    Affects Versions: 13.1.0, 13.2.0
>         Environment: CentOS 6 x64
>            Reporter: Ingenierie
>            Assignee: Joshua Colp
>         Attachments: backtrace_pipe_leak.txt, extensions-EAGI.conf, extensions-SayDigits.conf, pipes_leak.log, sip.conf
>
>
> Hello,
> Under some circumstances that I haven't determined yet, Asterisk will not close a pipe() that it has opened. This leads to the process file descriptor table filling up with pairs of pipes, like this:
> {noformat}asterisk 11128 asterisk  200w  FIFO                0,6        0t0 6057668 pipe
> asterisk 11128 asterisk  201r  FIFO                0,6        0t0 6057672 pipe
> asterisk 11128 asterisk  202w  FIFO                0,6        0t0 6057672 pipe
> asterisk 11128 asterisk  203r  FIFO                0,6        0t0 6057676 pipe
> asterisk 11128 asterisk  204w  FIFO                0,6        0t0 6057676 pipe
> {noformat}
> You can reproduce this issue with SIPp:
> {noformat}
> /sipp -i local_ip sip_proxy -sf scenario.xml -inf auth.csv  -r 5 -l 95 -mp 5606 -trace_err
> {noformat}
> Regards



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