asterisk users - Sep 2023 - Asterisk 18.14.0 vs 18.18.0 and chan_console/chan_alsa

>
>
> Not sure if this is the same thing you're seeing, but chan_console
> currently has a known deadlock issue that has not been resolved:
> https://issues-archive.asterisk.org/ASTERISK-30481
> It's quite easy to reproduce, so it may be the case that the module is
> currently unusable.
>
Well this is a bummer....

 [Sep  8 08:45:28] WARNING[313684][C-00000001]: chan_console.c:651
console_indicate: Don't know how to display condition 26 on Console/default
  --- <("<) --- Hangup on Console --- (>")> ---
[Sep  8 08:45:28] ERROR[313683]: utils.c:1027 lock_info_destroy: Thread
'stream_monitor       started at [  390] chan_console.c start_stream()'
still has a lock! - 'pvt' (0x55e647a245e0) from 'stream_monitor'
in
chan_console.c:281!

How do we get this working????

Jerry
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20230908/2d0183be/attachment.html>

>>> How do we get this working????
For the time being, go back to 18.14.0

Doug

So I have done through chan_console.c and searched for console_pct_lock() -
every one - has a matching console_pvt_unlock()

How is the deadlock occurring ?

jerry
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20230908/dee530c8/attachment.html>