[asterisk-bugs] [JIRA] (ASTERISK-29120) Crash: ast_bridge_channel_queue_frame on bridge softmix

[Joshua Elson (JIRA)]

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

Joshua Elson commented on ASTERISK-29120:
-----------------------------------------

Well... so was able to run on a few nodes, but virtually all of them began to experience a new issue when running under production load before I could get any fence violations from MALLOC_DEBUG.

The symptom was that the whole system would lock up after a few hours of use with these errors repeated a number of times in the logs:

```
NOTICE[48]: res_pjsip/pjsip_transport_management.c:170 idle_sched_cb: Shutting down transport 'WS to 127.0.0.1:51368' since no request was received in 32 seconds
WARNING[117930]: res_http_websocket.c:559 ws_safe_read: Web socket closed abruptly
```

We're running with pjproject cache, cache_pools=no, but not sure if there's anything I can do to prevent that issue or work around it to get a debug output on this.

Any ideas?

> Crash: ast_bridge_channel_queue_frame on bridge softmix
> -------------------------------------------------------
>
>                 Key: ASTERISK-29120
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29120
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Bridges/bridge_softmix
>    Affects Versions: 17.7.0
>         Environment: CentOS 7 fully patched
>            Reporter: Joshua Elson
>            Assignee: Joshua Elson
>         Attachments: asterisk-core-20201009-144056-brief.txt, asterisk-core-20201009-144056-full.txt, asterisk-core-20201009-144056-info.txt, asterisk-core-20201009-144056-locks.txt, asterisk-core-20201009-144056-thread1.txt
>
>
> Experiencing this crash daily as well on multiple identical servers in this bridged configuration. In this case, pjproject.conf cache_pools was set to no.



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