[asterisk-bugs] [Asterisk 0015867]: Corrupt Memory Issue - with Valgrind Trace

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15867 
====================================================================== 
Reported By:                leobrown
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15867
Category:                   Channels/chan_sip/General
Reproducibility:            random
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
JIRA:                       SWP-1125 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-09-09 15:58 CDT
Last Modified:              2010-05-04 16:20 CDT
====================================================================== 
Summary:                    Corrupt Memory Issue - with Valgrind Trace
Description: 
Hi,

Have a CentOS 5 system running Asterisk 1.6.0.9 (have tried more recent
builds too but know this version well) and it is becoming unstable when
loading IAX2. Once the module is loaded, the asterisk console prompt no
longer appears unless connecting remotely, and even then it only gives
output to some commands.

Without IAX2 loaded the system is stable for a few hours, or shall i say a
few calls.

I know that there can be an issue with corrupt memory, but i am not sure
what this points to. I have created a valgrind trace and hopefully this may
shed some light on what is at fault.

I should not also astcanary is tweeting. Everything else on the stable,
webserver etc are running fine and stable. The problem has persists through
multiple reboots and disk checks.

Cheers
Leo
====================================================================== 

---------------------------------------------------------------------- 
 (0121379) cappucinoking (reporter) - 2010-05-04 16:20
 https://issues.asterisk.org/view.php?id=15867#c121379 
---------------------------------------------------------------------- 
I don't think you should expect * to behave properly with a corrupt DB. 
So how about instead, an astdb diagnostics/consistancy verifier tool? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-04 16:20 cappucinoking  Note Added: 0121379                          
======================================================================