| Summary: | ASTERISK-23207: Crash on shutdown in ccss due to scheduler context already being destroyed in cc_generic_monitor_cancel_available_timer | ||
| Reporter: | Matt Jordan (mjordan) | Labels: | |
| Date Opened: | 2014-01-28 17:06:54.000-0600 | Date Closed: | 2017-12-18 10:57:29.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Core/CallCompletionSupplementaryServices |
| Versions: | 1.8.25.0 11.7.0 12.0.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) backtrace_9285.txt | |
| Description: | 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. | ||
| Comments: | By: Joshua C. Colp (jcolp) 2017-12-18 10:52:14.749-0600 Suspending as massive changes to shutdown have occurred and it has not been seen in years. By: Corey Farrell (coreyfarrell) 2017-12-18 10:57:29.266-0600 This was fixed by ASTERISK-24881. | ||