[asterisk-bugs] [JIRA] (ASTERISK-26721) Asterisk Crash - astobj2.c: FRACK!, Failed assertion bad magic number 0x0 for object 0x7fc9f402d088

Asterisk Team (JIRA) noreply at issues.asterisk.org
Mon Jan 16 10:19:10 CST 2017


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

Asterisk Team commented on ASTERISK-26721:
------------------------------------------

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].

> Asterisk Crash - astobj2.c: FRACK!, Failed assertion bad magic number 0x0 for object 0x7fc9f402d088
> ---------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-26721
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26721
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Addons/General
>    Affects Versions: 13.11.2, 13.13.1
>         Environment: - Ubuntu 14.04
> - HP ProLiant DL380 Gen G7
> - Digium, Inc. Wildcard TE820 octal-span T1/E1/J1 card 3.3V (PCI-Express) (rev 02)
>            Reporter: Félim Whiteley
>
> Under low or high load the server starts to get high CPU usage and call quality drops until the box becomes unusable. It's a production server so hard to run traces on as usually it occurs when there are a large amount of calls.
> I compiled in the DEBUG options from the troubleshooting guide and have attached a trace. The server had not fully crashed by this point but asterisk process was filling approximately 8 cores on the server at 100%. The only fix is a core restart.
> I can't recreate it but it happens almost every day, to alleviate the issue a graceful restart is scheduled each day during a known low call period, the box is required 24/7.
> Upgraded to 13.13.1 as an attempt to fix but still occurring.



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



More information about the asterisk-bugs mailing list