[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=206712#comment-206712 ] 

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

doing some more testing..  running asterisk under valgrind. the system is still running.. (albeit slowly.. fortunately a lab machine)... however shows some errors in valgrind right at startup...  

just for kicks I loaded up an identical machine in my VMware fusion..  basically copied the filesystem from the failing machine to a VM and booted it..  of course the bare metal on the macbook is Core -i7 vs the atom D525 that the issue occurs on..  but the valgrind.txt on the VMWware has no errors.. is it safe to say I have a hardware issue? or a Linux Kernel to hardware issue as opposed to an asterisk issue? im going to build an identical D525 machine to see if valgrind errors on it as well..

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