[asterisk-bugs] [JIRA] (ASTERISK-27859) Crash when freeing after bridge

Richard Mudgett (JIRA) noreply at issues.asterisk.org
Fri Jun 1 11:21:54 CDT 2018


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

Richard Mudgett commented on ASTERISK-27859:
--------------------------------------------

{quote}
0. jump from VMWare to bare metal platform ?
{quote}
Asterisk is a more real time type application and thus requires more responsiveness from the machine.  It depends upon what is happening on other virtual machines on the physical machine.
{quote}
1. jump to another OS (from Debian to CentOS) ?
{quote}
Asterisk doesn't really care which supported OS you use.
{quote}
2. use Certified-Asterisk instead of standard Asterisk (ie picking a precise Asterisk LTS version, not the lastest one) ?
{quote}
It is up to you to pick the version you want to use.  The supplied link describes certified asterisk and has a FAQ about certified asterisk.  Basically you get *no* special benefit to using certified asterisk over other versions unless you have a service level agreement with Digium.  Without a service level agreement any bug fixes resulting from an issue you have will not be put into the certified version.
https://www.digium.com/products/asterisk/certified-asterisk
{quote}
3. use binary Asterisk package instead of compiling from source ?
{quote}
I think compiling Asterisk from source is always better.  Precompiled distributions are either way behind or you cannot provide backtrace debug information if you have an issue.
{quote}
4. favor PJSIP over chansip (we tried both) ?
{quote}
chan_sip has no maintainer and is entirely community supported.  chan_pjsip is actively maintained and gets new features.
{quote}
5. use old tricks such as nightly or weekly reboots
{quote}

Basically you cannot avoid something if you don't know what triggers the problem.  We currently don't have enough information to know what triggers the problem let alone the root cause.

> Crash when freeing after bridge
> -------------------------------
>
>                 Key: ASTERISK-27859
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27859
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Bridging
>    Affects Versions: 13.20.0
>         Environment: Debian Stretch on VMWare. Asterisk compiled from source
>            Reporter: Olivier Krief
>            Assignee: Unassigned
>              Labels: pjsip
>         Attachments: core-brief.txt, core-full.txt, core-locks.txt, core-thread1.txt, debug_extract, syslog_extract
>
>
> Asterisk stops with the following message (from /var/log/syslog):
> May 16 12:11:07 localhost asterisk[3216]: *** Error in `/usr/sbin/asterisk': free(): invalid size: 0x00007f1a540db0a0 ***
> May 16 12:11:07 localhost asterisk[3216]: ======= Backtrace: =========
> May 16 12:11:07 localhost asterisk[3216]: /lib/x86_64-linux-gnu/libc.so.6(+0x70bfb)[0x7f1a6800dbfb]
> May 16 12:11:07 localhost asterisk[3216]: /lib/x86_64-linux-gnu/libc.so.6(+0x76fc6)[0x7f1a68013fc6]
> May 16 12:11:07 localhost asterisk[3216]: /lib/x86_64-linux-gnu/libc.so.6(+0x7780e)[0x7f1a6801480e]
> May 16 12:11:07 localhost asterisk[3216]: /usr/sbin/asterisk(ast_bridge_run_after_callback+0x11c)[0x56445a48b5cb]
> May 16 12:11:07 localhost asterisk[3216]: /usr/sbin/asterisk(+0x80032)[0x56445a481032]
> May 16 12:11:07 localhost asterisk[3216]: /usr/sbin/asterisk(+0x226d4e)[0x56445a627d4e]
> May 16 12:11:07 localhost asterisk[3216]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x7494)[0x7f1a69153494]
> May 16 12:11:07 localhost asterisk[3216]: /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f1a68085acf]



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



More information about the asterisk-bugs mailing list