[asterisk-bugs] [JIRA] (ASTERISK-24881) ast_register_atexit should only be used when absolutely needed

Asterisk Team (JIRA) noreply at issues.asterisk.org
Thu May 21 15:24:36 CDT 2015


     [ https://issues.asterisk.org/jira/browse/ASTERISK-24881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Asterisk Team updated ASTERISK-24881:
-------------------------------------

    Target Release Version/s: 13.4.0

> ast_register_atexit should only be used when absolutely needed
> --------------------------------------------------------------
>
>                 Key: ASTERISK-24881
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24881
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/General
>    Affects Versions: SVN, 11.16.0, 13.2.0
>            Reporter: Corey Farrell
>            Assignee: Corey Farrell
>            Severity: Minor
>      Target Release: 13.4.0
>
>
> We've had many issues related to {{core stop now}} or {{core restart now}} causing segmentation faults.  The solution to this is to change almost everything to use {{ast_register_cleanup}}.
> Exceptions:
> CDR: Flush records.
> res_musiconhold: Kill external applications.
> AstDB: Close the DB.
> canary_exit: Kill canary process.
> Although some changes from ast_register_atexit to ast_register_cleanup are not strictly necessary, the point is for nothing to use ast_register_atexit except where required.  For this reason the change is across the board.



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



More information about the asterisk-bugs mailing list