| Summary: | ASTERISK-28155: res_pjsip_mwi: Crash at shutdown due to order problem | ||
| Reporter: | Joshua C. Colp (jcolp) | Labels: | pjsip |
| Date Opened: | 2018-11-07 07:33:58.000-0600 | Date Closed: | |
| Priority: | Minor | Regression? | No |
| Status: | Open/New | Components: | Resources/res_pjsip_mwi |
| Versions: | 13.23.1 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) backtrace_12830.txt | |
| Description: | As shown with the attached backtrace it is possible for a crash to occur at shutdown due to a container going bye bye when it is then being used. We should do an audit for other cases of this too. | ||
| Comments: | By: Corey Farrell (coreyfarrell) 2018-11-07 07:58:09.327-0600 I don't have time to prepare a patch right now but I suspect adding ast_module_ref to load_module inside {{if (!ast_sip_get_mwi_disable_initial_unsolicited()) {}}, add ast_module_unref to the end of send_initial_notify_all should prevent the shutdown race. | ||