[asterisk-bugs] [JIRA] (ASTERISK-28377) Core dump hanging up unanswered channel

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-28377:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

> Core dump hanging up unanswered channel
> ---------------------------------------
>
>                 Key: ASTERISK-28377
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28377
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Sorcery
>    Affects Versions: 16.2.1, 16.3.0
>         Environment: x86_64 x86_64 x86_64 GNU/Linux (Centos 7.6.1810) running in a docker container on same OS
>            Reporter: David Dhuyvetter
>
> Using ARI
> 1) accept inbound channel
> 2) create outbound channel
> 3) bridge inbound channel to outbound
> 4) dial outbound and let dial timeout expire
> 5) hangup outbound channel and destroy bridge
> 5) hangup inbound channel
> This results in either messages like:
> [2019-04-09 14:58:14.291878] WARNING[401][C-00000001]: bridge.c:1851 bridge_impart_internal: Channel SIP/199.68.168.27-00000000 has a PBX thread and cannot be imparted into bridge 65da81c3-613f-4ad4-a094-98f6e4e6e2c9
> FRACK!, Failed assertion user_data is NULL (0) at line 942 in dial_bridge_after_cb of stasis/control.c
> [2019-04-09 14:58:14.307946] ERROR[401][C-00000001]: stasis/control.c:942 dial_bridge_after_cb: FRACK!, Failed assertion user_data is NULL (0)
> [2019-04-09 14:58:14.308661] ERROR[401][C-00000001]:   Got 11 backtrace records
> # 0: /usr/sbin/asterisk(__ao2_lock+0x1ed) [0x45d59d]
> # 1: /usr/lib64/asterisk/modules/res_stasis.so(+0x151f0) [0x7f8e86f0d1f0]
> # 2: /usr/sbin/asterisk() [0x477251]
> # 3: /usr/sbin/asterisk(ast_datastore_free+0x1c) [0x4ca98c]
> # 4: /usr/sbin/asterisk() [0x499e39]
> # 5: /usr/sbin/asterisk(__ao2_ref+0x25c) [0x45de5c]
> # 6: /usr/sbin/asterisk() [0x52046e]
> # 7: /usr/sbin/asterisk() [0x5210db]
> # 8: /usr/sbin/asterisk() [0x59a149]
> # 9: /lib64/libpthread.so.0(+0x7dd5) [0x7f8eaf191dd5]
> #10: /lib64/libc.so.6(clone+0x6d) [0x7f8eae533ead]
> or Segmentation Fault, or both



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