[asterisk-bugs] [JIRA] (ASTERISK-21806) Segfault in CHAN_SIP - Memory Allocation.
Richard Mudgett (JIRA)
noreply at issues.asterisk.org
Thu May 23 10:00:01 CDT 2013
[ https://issues.asterisk.org/jira/browse/ASTERISK-21806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206749#comment-206749 ]
Richard Mudgett commented on ASTERISK-21806:
--------------------------------------------
The last item found by valgrind (invalid free) looks to be a problem. It would depend on what other debug compile options in "make menuselect" are enabled.
What debug compile options do you have enabled?
DEBUG_THREADS - This will reduce system performance because it effectively serializes Asterisk's locking. It should only be enabled when looking for deadlocks.
MALLOC_DEBUG - This will compete with valgrind to the detriment of both tools. If this is enabled, the valgrind finding would be invalid. (I also consider this option quite useless before the improvements to it in newer versions.)
> 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
More information about the asterisk-bugs
mailing list