[asterisk-bugs] [JIRA] (ASTERISK-21893) Segfault after call hangup, in ast_channel_hangupcause_set, at channel_internal_api.c

[Nikola Ciprich (JIRA)]

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

Nikola Ciprich commented on ASTERISK-21893:
-------------------------------------------

hello, just wanted to let you know we're experiencing exactly same issue with asterisk 11.14.0, dahdi 2.10.0.1, libpri 1.4.15.
affected box is quite heavily used, 4x PRI, ~60/70 concurrent calls. we're using AMI originated calls a lot, CEL logging to postgresql, dialplan is dynamic, with connection to sqlitedb (via ODBC), otherwise nothing special. If I can help debug this issue, I'll be glad to provide any needed info. However due to heavy box usage, I'm afraid, I won't be able to use valgrind and similar :-(

> Segfault after call hangup, in ast_channel_hangupcause_set, at channel_internal_api.c
> -------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21893
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21893
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/General
>    Affects Versions: 11.2.1
>            Reporter: Alexandr Gordeev
>            Assignee: Alexandr Gordeev
>            Severity: Critical
>         Attachments: backtrace_20130514.txt, debug_20130514.txt, extensions.conf.txt
>
>
> {code}#0  0x080d0e68 in ast_channel_hangupcause_set (chan=0x0, value=16) at channel_internal_api.c:580
> #1  0xb5c244d2 in pri_dchannel (vpri=0xb5c40198) at sig_pri.c:7137
> #2  0x081b8735 in dummy_start (data=0x894c060) at utils.c:1028
> #3  0xb7257955 in start_thread () from /lib/i686/cmov/libpthread.so.0
> #4  0xb767e58e in clone () from /lib/i686/cmov/libc.so.6{code}



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