[asterisk-bugs] [JIRA] (ASTERISK-21806) Segfault in CHAN_SIP - Memory Allocation.

[Christopher (JIRA)]

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

Christopher commented on ASTERISK-21806:
----------------------------------------

in fact I have all 3 "common" debug options enabled.. 
Dont_optimize - as I was looking at core dumps.
Debug_threads - as it seemed asterisk deadlocked before the core dump so I wanted to be able to look at loks
malloc_debug - the docs were a bit confusing as it appeared to say turn it on even if running under valgrind.
perhaps the wiki should be updated to say "dont use this" when under valgrind..  I havent switched to the later "1.8" series as the certified will run the DPMA..  im not yet ready to make the jump to 11..
maybe the debug tools are actually causing some of my issues...  for now I will disable debug_threads and malloc_debug and run.. thus I can still analyze core dumps, correct? 
                
> Segfault in CHAN_SIP - Memory Allocation.
> -----------------------------------------
>
>                 Key: ASTERISK-21806
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21806
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 1.8.15.0
>         Environment: CPU: Atom D525, RAM 4GB, Fedora Linux, Kernel 2.6.43.8-1.i686
> 2 Aastra endpoints, 1 Polycom IP-650, 1 96 port SIP to analog gateway
> Asterisk 1.8.15-cert2
>            Reporter: Christopher
>         Attachments: core-dump-maxx-052213.txt, valgrind-052213-1530.txt, valgrind-good-052213-1930.txt
>
>
> Segfault occurs whether system is idle or is in-use. it will crash within a day or two even if 0 calls are made on it.  running under safe_asterisk, results in multiple crashes within a few minutes until eventually system ends up in a MUTEX lock. over 3 gigs of RAM available and plenty of disk space at time of first crash. Possibly related to the 96 port gateway producing 96 SIP registrations all at once?

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