[asterisk-bugs] [JIRA] (ASTERISK-26421) Segmentation Fault with ARI originate into mixing bridge with 43 clients

[Andrew Nagy (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-26421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Nagy updated ASTERISK-26421:
-----------------------------------

    Description: 
Asterisk crashed in the middle of our dangerous demo. We setup a system that would get an SMS then make an outbound call and bridge that call in. At around 43 calls Asterisk was at about 177% cpu. Because we lost the Dangerous Demo because of an Asterisk crash we'd like this moved to our L4 support for immediate fixing. Then please bring back everyone for Astricon's Dangerous Demos so that we can try this again.
.
.
.
.
.
.
.
.
.
.
.
.






Just kidding. This is not a priority I am just attaching the backtrace incase it's relevant for anyone.

Thanks for all you do and thank for Astricon! 

  was:
Asterisk crashed in the middle of our dangerous demo. We setup a system that would get an SMS then make an outbound call and bridge that call in. At around 43 calls Asterisk was at about 177% cpu. Because we lost the Dangerous Demo because of an Asterisk crash we'd like this moved to our L4 support for immediate fixing. Then please bring back everyone for Astricon's Dangerous Demos so that we can try this again.






Just kidding. This is not a priority I am just attaching the backtrace incase it's relevant for anyone.

Thanks for all you do and thank for Astricon! 


> Segmentation Fault with ARI originate into mixing bridge with 43 clients
> ------------------------------------------------------------------------
>
>                 Key: ASTERISK-26421
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26421
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.11.2
>            Reporter: Andrew Nagy
>            Severity: Minor
>         Attachments: backtrace.txt
>
>
> Asterisk crashed in the middle of our dangerous demo. We setup a system that would get an SMS then make an outbound call and bridge that call in. At around 43 calls Asterisk was at about 177% cpu. Because we lost the Dangerous Demo because of an Asterisk crash we'd like this moved to our L4 support for immediate fixing. Then please bring back everyone for Astricon's Dangerous Demos so that we can try this again.
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> .
> Just kidding. This is not a priority I am just attaching the backtrace incase it's relevant for anyone.
> Thanks for all you do and thank for Astricon! 



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