[asterisk-bugs] [JIRA] (ASTERISK-26973) bridge: Crash when freeing frame and snooping

[Kevin Harwell (JIRA)]

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

Kevin Harwell commented on ASTERISK-26973:
------------------------------------------

Also, since I am unable to currently replicate, and if it is possible try installing another version of Asterisk between 13.15 and your previous version (13.10). If it doesn't crash that will help narrow down what version the problem was introduced. Then it might be easier to find exactly what patch caused it.

For instance, I'd suggest starting with 13.13.0. If you install 13.13.0 and it does not crash then that tells us the problem was introduced in 13.14 or 13.15. If it does then the problem was probably introduced in 13.13 or below (13.12 or 13.11). Then you can install one of those versions and run again.

You can find the various versions you would need at the following:
https://downloads.asterisk.org/pub/telephony/asterisk/old-releases/

> bridge: Crash when freeing frame and snooping
> ---------------------------------------------
>
>                 Key: ASTERISK-26973
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26973
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Bridges/bridge_simple, Resources/res_stasis_snoop
>    Affects Versions: 13.15.0
>         Environment: Linux 2.6.32-642.11.1.el6.x86_64 #1 SMP Fri Nov 18 19:25:05 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>            Reporter: Michel R. Vaillancourt
>            Assignee: Kevin Harwell
>         Attachments: ARI.snoop.code, backtrace-and-debug.tgz, core.22813.backtrace.txt, core.asterisk.15474.backtrace.txt
>
>
> {noformat}
> [Apr 26 00:11:24]     -- Channel Snoop/[REDACTED]-00000002 joined 'simple_bridge' stasis-bridge <br6308>
> [Apr 26 00:11:28]   == Setting global variable 'SIPDOMAIN' to '[REDACTED]'
> [Apr 26 00:11:28]     -- Executing [[REDACTED]@inbound:1] Verbose("PJSIP/[REDACTED]-0000395a", "2, Call from "[REDACTED]" <[REDACTED]> to [REDACTED]") in new stack
> [Apr 26 00:11:28]   ==  Call from "[REDACTED]" <[REDACTED]> to [REDACTED]
> [Apr 26 00:11:28]     -- Executing [[REDACTED]@inbound:2] Stasis("PJSIP/[REDACTED]-0000395a", "[REDACTED],external") in new stack
> [Apr 26 00:11:30]     -- <PJSIP/[REDACTED]-00003894> Playing 'beep.slin16' (language 'en')
> [Apr 26 00:11:30]     -- Channel PJSIP/[REDACTED]-0000395a joined 'simple_bridge' stasis-bridge <[REDACTED]>
> [Apr 26 00:11:30]        > 0x7fbc741cd8a0 -- Probation passed - setting RTP source address to [REDACTED]:17564
> asterisk2*CLI>
> Disconnected from Asterisk server
> [Apr 26 00:11:31] Asterisk cleanly ending (0).
> [Apr 26 00:11:31] Executing last minute cleanups
> Asterisk ending (0).
> {noformat}
> We upgraded one dev PBX and one production PBX to 13.15.0 and have discovered that suddenly a function that worked just fine before now causes Asterisk to SegFault.  Note that this ARI code function has been stable / safe for over a year;  the behavior began as soon as we upgraded.  
> Our DEV and PRD machines still running prior versions of Asterisk using the same ARI code do not exhibit this behavior.



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