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

[David Brillert (JIRA)]

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

David Brillert commented on ASTERISK-22540:
-------------------------------------------

We already include that fix since it was committed to our SVN r399516 install.
That's probably what made some of the memleaks disappear and allowed us to focus on the remote attack as the culprit.
Now this is starting to look like a different bug report and I should think about closing this one out.  Since SVN r399516 has only been in for 4 days I'll leave it open for a while longer in case the segfault does come 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
>         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