Summary:	ASTERISK-26931: FRACK!, Failed assertion bad magic number framehook_detach()
Reporter:	Ross Beer (rossbeer)	Labels:
Date Opened:	2017-04-10 03:30:14	Date Closed:	2017-04-26 15:29:08
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Core/Bridging
Versions:	GIT	Frequency of Occurrence	Occasional
Related Issues:
Environment:	Fedora 23 GIT Version :Asterisk GIT-13-13.15.0-rc1-64-ge851412M There is also a patch applied (gerrit 5341): rtp_engine/res_rtp_asterisk: Fix RTP struct reentrancy crashes.	Attachments:
Description:	While watching the CLI, the following output is shown: {noformat}[2017-04-10 09:21:52] ERROR[78597][C-00000c4b]: astobj2.c:131 INTERNAL_OBJ: FRACK!, Failed assertion bad magic number 0x45504547 for object 0x7f6de4002080 (0) Got 29 backtrace records #0: [0x6085d2] main/utils.c:2477 __ast_assert_failed() (0x608545+8D) #1: [0x45e02b] main/astobj2.c:132 INTERNAL_OBJ() #2: [0x45e68e] main/astobj2.c:399 internal_ao2_ref() #3: [0x45ead1] main/astobj2.c:519 __ao2_ref() (0x45eaa3+2E) #4: [0x45eb42] main/astobj2.c:533 __ao2_cleanup() (0x45eb1e+24) #5: [0x527c0b] main/framehook.c:82 framehook_detach() #6: [0x527d55] main/framehook.c:109 framehook_list_push_event() #7: [0x528682] main/framehook.c:323 ast_framehook_list_read_event() (0x52865a+28) #8: [0x4b8d4e] main/channel.c:3959 __ast_read() #9: [0x4ba88f] main/channel.c:4385 ast_read() (0x4ba872+1D) #10: [0x4874fd] main/bridge_channel.c:2416 bridge_handle_trip() #11: [0x4879a8] main/bridge_channel.c:2586 bridge_channel_wait() #12: [0x488093] main/bridge_channel.c:2730 bridge_channel_internal_join() (0x487b79+51A) #13: [0x46e97d] main/bridge.c:1712 ast_bridge_join() (0x46e712+26B) #14: [0x50fe83] main/features.c:681 ast_bridge_call_with_flags() (0x50fcdc+1A7) #15: [0x50ff55] main/features.c:712 ast_bridge_call() (0x50ff28+2D) #16: [0x7f6ccdb697f1] apps/app_dial.c:3205 dial_exec_full() #17: [0x7f6ccdb69b82] apps/app_dial.c:3262 dial_exec() #18: [0x589d20] main/pbx_app.c:484 pbx_exec() (0x589c07+119) #19: [0x577748] main/pbx.c:2884 pbx_extension_helper() #20: [0x57abff] main/pbx.c:4109 ast_spawn_extension() (0x57abaf+50) #21: [0x57b868] main/pbx.c:4284 __ast_pbx_run() #22: [0x57cf94] main/pbx.c:4605 pbx_thread() #23: [0x6055c7] main/utils.c:1235 dummy_start() {noformat}
Comments:	By: Asterisk Team (asteriskteam) 2017-04-10 03:30:15.793-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: Rusty Newton (rnewton) 2017-04-12 17:52:27.141-0500 Ross, what GIT commit is in use? Can you get a refs.txt for the issue? In addition you probably want to simultaneously gather a debug log (or at least a full/verbose log) so we can see what is happening up until this point. By: Rusty Newton (rnewton) 2017-04-12 18:00:12.110-0500 Oh, and of course provide the full backtrace as usual. By: Ross Beer (rossbeer) 2017-04-13 03:15:17.839-0500 GIT Version :Asterisk GIT-13-13.15.0-rc1-64-ge851412M There is also a patch applied (gerrit 5341): rtp_engine/res_rtp_asterisk: Fix RTP struct reentrancy crashes. I have a feeling this may be fixed gerrit commit 5433, however, I am waiting for the merge conflict to be fixed with the above patch before testing. By: Rusty Newton (rnewton) 2017-04-24 20:41:21.453-0500 Ross, any update on further testing with this one? By: Ross Beer (rossbeer) 2017-04-24 21:35:13.591-0500 Asterisk didn't generate a core dump, therefore, didn't get a backtrace. The issue hasn't repeated since updating to the latest GIT version, I will continue to monitor to confirm that the issue is resolved. Thank you for your assistance. By: Rusty Newton (rnewton) 2017-04-26 15:29:08.624-0500 Alright. I'm closing it, but it should reopen automatically if you comment again with an update.