[asterisk-bugs] [JIRA] (ASTERISK-20507) MWI Refcount Error causing segfault

[Matt Jordan (JIRA)]

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

Matt Jordan updated ASTERISK-20507:
-----------------------------------

    Component/s: Channels/chan_sip/Subscriptions
    
> MWI Refcount Error causing segfault
> -----------------------------------
>
>                 Key: ASTERISK-20507
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20507
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/Subscriptions
>    Affects Versions: 1.8.16.0
>         Environment: Debian 
>  2.6.26-2-686 #1 SMP Wed Sep 21 04:35:47 UTC 2011 i686 GNU/Linux
>            Reporter: Andrew Parisio
>            Severity: Critical
>         Attachments: backtrace 10-2.txt, backtrace 10-3.txt
>
>
> A few weeks ago asterisk started randomly segfaulting with 1.8.13.0 so I updated to 1.8.16.0.  It always happens when the AMI originates a call, this is what the console log outputs, including 500 to 700 refcount errors on every single one of these crashes (it's happened 15 or so times now):
> [2012-10-03 10:54:34] VERBOSE[11631] manager.c:   == Manager 'Admin' logged on from 192.168.11.3
> [2012-10-03 10:54:34] VERBOSE[11632] pbx.c:     -- Executing [1811 at inside-leg:1] SIPAddHeader("Local/1811 at inside-leg-6afa;2", "Call-Info:<sip:>;answer-after=0") in new stack
> [2012-10-03 10:54:34] VERBOSE[11632] pbx.c:     -- Executing [1811 at inside-leg:2] Dial("Local/1811 at inside-leg-6afa;2", "SIP/1811,20") in new stack
> [2012-10-03 10:54:34] ERROR[11632] astobj2.c: refcount -1 on object 0xacc24608
> [2012-10-03 10:54:34] ERROR[11632] astobj2.c: refcount -2 on object 0xacc24608
> [2012-10-03 10:54:34] ERROR[11632] astobj2.c: refcount -3 on object 0xacc24608
> After the last refcount error the log ends, and asterisk core dumps.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira