[asterisk-bugs] [JIRA] (ASTERISK-21695) Crash Asterisk

[Richard Mudgett (JIRA)]

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

Richard Mudgett commented on ASTERISK-21695:
--------------------------------------------

These crashes are from memory corruption just like the previous issue ASTERISK-20830.
Valgrind output or MALLOC_DEBUG output from *Asterisk v1.8.20* or newer is needed.  Asterisk v1.8.20 improved MALLOC_DEBUG to catch and detect more problems.

The MALLOC_DEBUG mmlog from an earlier Asterisk version you have provided is showing some fence violations.  The improved MALLOC_DEBUG from Asterisk v1.8.20 or newer should give better information.
                
> Crash Asterisk
> --------------
>
>                 Key: ASTERISK-21695
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21695
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 1.8.19.0
>            Reporter: Osvaldo Tuphiq Smera Neto
>            Assignee: Osvaldo Tuphiq Smera Neto
>            Severity: Critical
>         Attachments: backtrace2404.txt, backtrace250415.txt, backtrace250417.txt, backtrace-threads.txt, mmlog
>
>
> Open to question ASTERISK-20830, where there's no asterisk crash after some time of use. Be finding the memory, changed server and resolved. To my surprise, after 3 months of use, the crash's occur again, as before, at the same time every day. Interestingly, just as occurred in another server, slow to occur, occur at the same time, and I'm afraid to go and also pass to run more than once a day. Here's the last 2 core and mmlog.

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