[asterisk-bugs] [JIRA] (ASTERISK-22540) WARNING[2324] asterisk.c: Fork failed: Cannot allocate memory in /var/log/asterisk/messages then segfault

Richard Mudgett (JIRA) noreply at issues.asterisk.org
Tue Sep 17 18:53:03 CDT 2013


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

Richard Mudgett commented on ASTERISK-22540:
--------------------------------------------

It is a quirk of the issue tracker.  It seems to be loath to have issues unassigned.

When feedback is requested, the issue is assigned to the requested person.  If the issue was previously unassigned it does not unassign the issue when the issue sent back.
                
> WARNING[2324] asterisk.c: Fork failed: Cannot allocate memory in /var/log/asterisk/messages then segfault
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-22540
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22540
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 11.5.1
>         Environment: SVN r398885
>            Reporter: David Brillert
>            Assignee: David Brillert
>         Attachments: gdb-c core asterisk.txt, messages.rar, valgrind.rar
>
>
> Asterisk eats memory until it crashes.
> Attached valgrind log and bt full from core file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list