| Summary: | ASTERISK-28338: Asterisk crashes with ERROR *** /usr/sbin/asterisk': corrupted size vs. prev_size: 0x00007f77400cfcf0 *** when there are 48 SIP outbound calls.(almost 144 SIP Channels) | ||||
| Reporter: | Talha Omair (TalhaOmair) | Labels: | pjsip webrtc | ||
| Date Opened: | 2019-03-15 12:47:19 | Date Closed: | 2019-03-21 13:37:08 | ||
| Priority: | Major | Regression? | Yes | ||
| Status: | Closed/Complete | Components: | . I did not set the category correctly. | ||
| Versions: | 16.2.1 | Frequency of Occurrence | Frequent | ||
| Related Issues: |
| ||||
| Environment: | Ubuntu 16.04 Kernel 4.4.0-96-generic x86_64 CPU(s) 4 Model Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz | Attachments: | ( 0) asterisk.crash ( 1) CoreDump.tar.gz ( 2) CoreDump-brief.txt ( 3) CoreDump-full.txt ( 4) CoreDump-locks.txt ( 5) CoreDump-thread1.txt ( 6) logs.txt | ||
| Description: | Asterisk installed from source following this link https://wiki.asterisk.org/wiki/display/AST/Installing+Asterisk+From+Source.Also configure using ./configure --with-jansson-bundled --with-pjproject-bundled.
Asterisk crashes when dialing outbound sip calls using stasis app. In stasis app agent logged in using webRTC, stasis dial outbound channel then create bridge and add this channel to this bridge. Then dial agent channel and add to same bridge. Also there is a recording channel as well for this call. It's working absolutely fine with asterisk version 14.4.1. But when upgrade version to 16.2.1 this issue happened. Error Message in log is: asterisk[1375]: *** Error in `/usr/sbin/asterisk': corrupted size vs. prev_size: 0x00007f77400cfcf0 *** | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2019-03-15 12:47:19.831-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]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. By: Benjamin Keith Ford (bford) 2019-03-15 13:11:28.391-0500 Thanks for your report! Could you check to see if this happens in versions earlier than 16.2.1? If we can get an idea of when this started happening, then maybe we can track down a commit that exposed this behavior. Also, you no longer need to configure "--with-pjproject-bundled" in 15+; it's done for you :) By: Talha Omair (TalhaOmair) 2019-03-15 13:16:53.714-0500 * If we can get an idea of when this started happening, then maybe we can track down a commit that exposed this behavior. * I surely can do it for you but its affecting my production and I am busy to handle it. I am really sorry. :( * Also, you no longer need to configure "--with-pjproject-bundled" in 15+; it's done for you * As I upgrade it from 14.4.1 to 16.2.1 without --with-pjproject-bundled it did not upgrade pjsip version. That's why I did this. By: Benjamin Keith Ford (bford) 2019-03-18 11:09:57.292-0500 I understand. If you are able to check earlier versions at some point, give it a go and let me know what the results are. It would help narrow down the problem. As for the crash, can you follow the guidelines found here [1] on how to get a backtrace, and attach those files to the issue? [1]: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace By: Talha Omair (TalhaOmair) 2019-03-19 08:01:52.917-0500 * I understand. If you are able to check earlier versions at some point, give it a go and let me know what the results are. It would help narrow down the problem. Sure, I will let you now regarding earlier versions. Also, tarball of backtrace using mentioned link has been attached. By: Benjamin Keith Ford (bford) 2019-03-19 08:42:14.287-0500 Attaching core dump files By: Benjamin Keith Ford (bford) 2019-03-21 13:36:26.079-0500 From the backtrace, it looks like this issue may have the same root cause as ASTERISK-28161 since both appear to be in the PJSIP timer code. I'm going to close this issue out as a duplicate and link it to the before-mentioned issue. If you have any more information, post it on that issue so we can keep everything in one spot. As for the patch in the comments, it is currently in 16.2.1 so it does not fix this problem. | ||||