[asterisk-bugs] [JIRA] (ASTERISK-29187) stasis.c:1474 FRACK!, Failed assertion bad magic number 0x0 for object in publish_msg

Asterisk Team (JIRA) noreply at issues.asterisk.org
Mon Nov 30 12:49:16 CST 2020


    [ https://issues.asterisk.org/jira/browse/ASTERISK-29187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252859#comment-252859 ] 

Asterisk Team commented on ASTERISK-29187:
------------------------------------------

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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

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.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> stasis.c:1474 FRACK!, Failed assertion bad magic number 0x0 for object in publish_msg
> -------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-29187
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29187
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_stasis
>    Affects Versions: 17.8.0, 18.0.1
>         Environment: Kubernetes pod running on a Container Optimized OS (GCE) instance
>            Reporter: Mauri de Souza Meneguzzo (3CPlus)
>
> This is a follow up for ASTERISK-28931, which we opened some time ago. Seems like the same problem is happening again.
> This problem started on Asterisk 17.3.0 and is happening in every version onwards. We are currently running version 18.0.1 and the segfault still occurs.
> Our Asterisk instances are crashing at least one time per day with the following backtrace being displayed:
> FRACK!, Failed assertion bad magic number 0x0 for object 0x7fa328020c60 (0) at line 1474 in publish_msg of stasis.c
> # 0: asterisk __ast_assert_failed()
> # 1: asterisk <unknown>()
> # 2: asterisk __ao2_ref() 
> # 3: asterisk <unknown>() 
> # 4: asterisk stasis_publish() 
> # 5: asterisk bridge_topics_destroy() 
> # 6: asterisk <unknown>() 
> # 7: asterisk __ao2_ref() 
> # 8: asterisk <unknown>() 
> # 9: asterisk __ao2_ref() 
> #10: asterisk ast_bridge_depart() 
> #11: [0x7fa33f7c16c0] res_stasis.so res_stasis.c:1567 stasis_app_exec() 
> #12: [0x7fa33f02e310] app_stasis.so app_stasis.c:105 app_exec() 
> #13: asterisk pbx_exec() 
> #14: asterisk <unknown>() 
> #15: asterisk ast_spawn_extension() 
> #16: asterisk <unknown>() 
> #17: asterisk <unknown>() 
> #18: asterisk <unknown>() 
> #19: [0x7fa350359ea7] libpthread.so.0 pthread_create.c:478 start_thread() 
> #20: [0x7fa34ffb0d4f] libc.so.6 clone.S:97 __GI___clone() 
> 26 Segmentation fault (core dumped) asterisk  -fg



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list