[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:all-tabpanel ]

David Brillert updated ASTERISK-22540:
--------------------------------------

    Status: Waiting for Feedback  (was: Waiting for Feedback)

Rev 398939 was installed to combat memory leaks we were seeing when we were already at Rev 397604
We were hoping commit 398103 was going to solve those leaks.
So I presume to answer your question, I don't know which commit may have caused the leaks or if this is a current regression.

#0  0x0000003d3fc45071 in sqlite3VdbeMemRelease () from /usr/lib64/libsqlite3.so.0
No symbol table info available.
#1  0x0000003d3fc45821 in sqlite3VdbeMemSetStr () from /usr/lib64/libsqlite3.so.0
No symbol table info available.
#2  0x0000003d3fc3c5d8 in sqlite3Error () from /usr/lib64/libsqlite3.so.0
No symbol table info available.
#3  0x0000003d3fc41f39 in ?? () from /usr/lib64/libsqlite3.so.0
No symbol table info available.
#4  0x0000003d3fc41ff8 in ?? () from /usr/lib64/libsqlite3.so.0
No symbol table info available.
#5  0x0000000000493fc1 in ast_db_gettree ()
No symbol table info available.
#6  0x00002b5c1dd995b3 in process_clearcache (ignore=<value optimized out>) at pbx_dundi.c:2208
        db_entry = 0x2b5bf91e9cd0
        db_tree = 0x0
        now = 1379297393
        __PRETTY_FUNCTION__ = "process_clearcache"

The core dump leads me to believe the problem is in sqlite3 and the last commit according to the logs that touched sqlite3 was 

Revision 375763 - Directory Listing
Modified Sun Nov 4 01:17:25 2012 UTC (10 months, 1 week ago) by mjordan

Properly finalize prepared SQLite3 statements to prevent memory leak

The AstDB uses prepared SQLite3 statements to retrieve data from the SQLite3
database.  These statements should be finalized during Asterisk shutdown so
that the SQLite3 database can be properly closed.  Failure to finalize the
statements results in a memory leak and a failure when closing the database.

This patch fixes those issues by ensuring that all prepared statements are
properly finalized at shutdown.

(closes issue ASTERISK-20647)
Reported by: Corey Farrell
patches:
  astdb-sqlite3_close.patch uploaded by Corey Farrell (license 5909)
........

Merged revisions 375761 from http://svn.asterisk.org/svn/asterisk/branches/10
                
> 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