[asterisk-bugs] [JIRA] (ASTERISK-23207) Crash on shutdown in ccss due to scheduler context already being destroyed in cc_generic_monitor_cancel_available_timer

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-23207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan updated ASTERISK-23207:
-----------------------------------

    Attachment: backtrace_9285.txt
    
> Crash on shutdown in ccss due to scheduler context already being destroyed in  cc_generic_monitor_cancel_available_timer
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-23207
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23207
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/CallCompletionSupplementaryServices
>    Affects Versions: 1.8.25.0, 11.7.0, 12.0.0
>            Reporter: Matt Jordan
>         Attachments: backtrace_9285.txt
>
>
> Caught by the Asterisk Test Suite. Backtrace is attached to the issue.
> When this occurs, Asterisk is shutting down and has already destroyed the scheduler context. As a result, when the timer is cancelled the scheduler is already disposed of, resulting in a crash when ast_sched_thread_del is called.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira