| Summary: | ASTERISK-27819: Asterisk Crash - astobj2.c: FRACK!, Failed assertion bad magic number 0x0 for object 0x7fc9f402d088 | ||
| Reporter: | vikas (vikas4793) | Labels: | |
| Date Opened: | 2018-04-20 01:25:24 | Date Closed: | 2020-01-14 11:13:59.000-0600 |
| Priority: | Critical | Regression? | |
| Status: | Closed/Complete | Components: | Channels/chan_sip/General |
| Versions: | 13.20.0 15.3.0 | Frequency of Occurrence | Frequent |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Asterisk Crash - astobj2.c: FRACK!, Failed assertion bad magic number 0x0 for object 0x7fc9f402d088
Got 10 backtrace records #0: [0x45b2f6] /usr/sbin/asterisk(__ao2_ref+0xa6) [0x45b2f6] #1: [0x7f7f215342a2] /usr/lib64/asterisk/modules/chan_sip.so(+0x712a2) [0x7f7f215342a2] #2: [0x5ad10d] /usr/sbin/asterisk(ast_sched_runq+0x12d) [0x5ad10d] #3: [0x7f7f215200a6] /usr/lib64/asterisk/modules/chan_sip.so(+0x5d0a6) [0x7f7f215200a6] #4: [0x5e9a6e] /usr/sbin/asterisk() [0x5e9a6e] [Apr 20 11:38:3324] NOTICE[18777]: chan_sip.c:24701 handle_response_peerpoke: Peer 'PW04827' is now Reachable. (53ms / 2000ms) [Apr 20 11:38:25] ERROR[17909]: chan_sip.c:16611 sip_poke_peer_s: FRACK!, Failed assertion bad magic number 0x7f7d for object 0x7f7d38004298 (0) Got 10 backtrace records #0: [0x45b2f6] /usr/sbin/asterisk(__ao2_ref+0xa6) [0x45b2f6] #1: [0x7f7f215342a2] /usr/lib64/asterisk/modules/chan_sip.so(+0x712a2) [0x7f7f215342a2] #2: [0x5ad10d] /usr/sbin/asterisk(ast_sched_runq+0x12d) [0x5ad10d] #3: [0x7f7f215200a6] /usr/lib64/asterisk/modules/chan_sip.so(+0x5d0a6) [0x7f7f215200a6] #4: [0x5e9a6e] /usr/sbin/asterisk() [0x5e9a6e] [Apr 20 11:38:33 | ||
| Comments: | By: Asterisk Team (asteriskteam) 2018-04-20 01:25:25.442-0500 The severity of this issue has been automatically downgraded from "Blocker" to "Major". The "Blocker" severity is reserved for issues which have been determined to block the next release of Asterisk. This severity can only be set by privileged users. If this issue is deemed to block the next release it will be updated accordingly during the triage process. By: Asterisk Team (asteriskteam) 2018-04-20 01:25:25.770-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: Asterisk Team (asteriskteam) 2018-04-20 01:25:26.022-0500 The module you are reporting the issue against is no longer supported as a core module but your issue is in the queue. Your patience is appreciated as a community developer may work the issue when time and resources become available. Asterisk is an open source project and community members work the issues on a voluntary basis. You are welcome to develop your own patches and submit them to the project.[1] If you are not a programmer and you are in a hurry to see a patch provided then you might try rallying support on the Asterisk users mailing list or forums.[2] Another alternative is offering a bug bounty on the asterisk-dev mailing list.[3] Often a little incentive can go a long way. [1]: https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process [2]: http://www.asterisk.org/community/discuss [3]: https://wiki.asterisk.org/wiki/display/AST/Asterisk+Bug+Bounties By: Kevin Harwell (kharwell) 2018-04-20 09:23:27.908-0500 Thank you for the crash report. However, we need more information to investigate the crash. Please provide: 1. A backtrace generated from a core dump using the instructions provided on the Asterisk wiki [1]. 2. Specific steps taken that lead to the crash. 3. All configuration information necesary to reproduce the crash. [1]: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace By: Asterisk Team (asteriskteam) 2018-05-04 12:00:01.326-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 | ||