| Summary: | ASTERISK-26725: astobj2.c: FRACK!, Failed assertion bad magic number | ||||||
| Reporter: | Dmitriy Serov (Demon) | Labels: | |||||
| Date Opened: | 2017-01-17 14:40:43.000-0600 | Date Closed: | 2017-01-18 08:31:37.000-0600 | ||||
| Priority: | Major | Regression? | |||||
| Status: | Closed/Complete | Components: | Resources/res_pjsip | ||||
| Versions: | 13.13.1 | Frequency of Occurrence | Constant | ||||
| Related Issues: |
| ||||||
| Environment: | Attachments: | ( 0) assertions-1.txt ( 1) assertions-2.txt ( 2) syslog.txt | |||||
| Description: | Installing asterisk 13.13.1 on ubuntu server with bundled pjproject.
Asterisk segfaults a lot of time (attachment syslog.txt) Two attachemts with assertion logs. I beg you at least to tell workarounds ASAP. | ||||||
| Comments: | By: Asterisk Team (asteriskteam) 2017-01-17 14:40:43.977-0600 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: Joshua C. Colp (jcolp) 2017-01-17 14:55:04.139-0600 Awaiting attachments. By: Dmitriy Serov (Demon) 2017-01-17 15:18:50.000-0600 syslog.txt - grep from syslog assertions-1.txt, assertions-2.txt - cut from asterisk logs. sorry. attached it to ASTERISK-25528 (mistake) By: Joshua C. Colp (jcolp) 2017-01-17 15:20:26.184-0600 What sort of environment is this under? Are you using WebRTC? Websockets? TCP? TLS? By: Dmitriy Serov (Demon) 2017-01-17 15:22:56.972-0600 ubuntu zesty (temporary server) with latest packages. PJSIP: UDP, TCP, TLS. a lot of endpoints and registrations. + chan_sip (a little) on other port. By: Richard Mudgett (rmudgett) 2017-01-17 18:18:54.401-0600 These assertion backtraces are not that useful. They can only say that a task processor job/task somewhere in res_pjsip was trying to lock a destroyed ao2 object. Enabling BETTER_BACKTRACES and DONT_OPTIMIZE would provide more information in those assertion backtraces. Since this is dealing with a destroyed ao2 object, turning on MALLOC_DEBUG will likely provide even better information from a segfault when it tries to use the destroyed object. By: Joshua C. Colp (jcolp) 2017-01-18 08:31:37.499-0600 Looking further we already have an issue tracking this, ASTERISK-26699. | ||||||