[asterisk-bugs] [JIRA] (ASTERISK-27753) bridge: Crash when freeing after bridge data after transfer occurs

[Olivier Krief (JIRA)]

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

Olivier Krief commented on ASTERISK-27753:
------------------------------------------

I am are planning to change, in 7 hours from now, my machine settings:
with DEBUG level set to 5
with DONT_OPTIMIZE and BETTER_BACKTRACES compiler flags.

Usually, it segfaults every two monthes or so.

What kind of feedback is waited from me now ?
Shall I wait for next issue to happen and then update core and log files with fresh ones ?



> bridge: Crash when freeing after bridge data after transfer occurs
> ------------------------------------------------------------------
>
>                 Key: ASTERISK-27753
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27753
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 13.19.0
>         Environment: Debian Stretch on VMWare. Asterisk compiled from source.
>            Reporter: Olivier Krief
>            Assignee: Olivier Krief
>         Attachments: core-brief.txt, core-full.txt, core-locks.txt, core-thread1.txt, full, syslog
>
>
> From time to time (once every two months or so), Asterisk exits with segfault without prior error message.
> Log file includes both lines bellow (and nothing between them):
> [2018-03-20 15:48:01] VERBOSE[4893][C-0005a469] pbx.c: Spawn extension (from-Foobar, 0326473958, 1) exited non-zero on 'SIP/Foobar2-000b649e'
> [2018-03-20 15:49:49] Asterisk 13.19.0 built by root @ Sipaccess-prod_2 on a x86_64 running Linux on 2018-02-08 23:12:35 UTC
> Lastest line shows Asterisk exited without being required to.
> I would expect Asterisk not to exit even if being mis-configured.



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