| Summary: | ASTERISK-26209: res_pjsip: Crash when unregistering dialog during subscription reconstruction | ||
| Reporter: | Ross Beer (rossbeer) | Labels: | |
| Date Opened: | 2016-07-18 10:20:21 | Date Closed: | 2020-01-14 11:13:44.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_pjsip |
| Versions: | 13.9.1 13.10.0-rc1 | Frequency of Occurrence | Frequent |
| Related Issues: | |||
| Environment: | Fedora Server 23 | Attachments: | ( 0) 20160728-backtrace.txt ( 1) backtrace_2016-07-18_16-15.txt |
| Description: | Repeated ABORTS in pjsip_ua_unregister_dlg (libasteriskpj.so) when using bundled PJSIP. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2016-07-18 10:20:21.869-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: George Joseph (gjoseph) 2016-07-20 12:19:04.406-0500 Ross, can you recompile with DONT_OPTIMIZE (you can uncheck COMPILE_DOUBLE) and BETTER_BACKTRACES? There aren't even any line numbers in the backtrace. By: Ross Beer (rossbeer) 2016-07-21 06:43:00.853-0500 For some reason core dumps are not being crated on Fedora 23 for all crashes. The provided backtrace was from the logs By: Joshua C. Colp (jcolp) 2016-07-24 17:06:43.788-0500 Have any of the suggestions and comments provided on the list helped? Without line numbers and further backtrace info it's extremely hard to isolate. By: Ross Beer (rossbeer) 2016-07-28 08:22:32.811-0500 I have just uploaded a full backtrace for the issue. Hopefully this will help resolve this issue. By: Joshua C. Colp (jcolp) 2016-07-28 13:47:08.222-0500 Can you open the core dump using gdb, perform the following, and attach the results: thread 1 frame 0 print *dlg By: Asterisk Team (asteriskteam) 2016-08-12 12:00:00.939-0500 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines | ||