[asterisk-bugs] [Asterisk 0015616]: random crashes

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15616 
====================================================================== 
Reported By:                rgj
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15616
Category:                   General
Reproducibility:            unable to reproduce
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.26 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-07-30 14:26 CDT
Last Modified:              2009-09-15 16:27 CDT
====================================================================== 
Summary:                    random crashes
Description: 
Our production Asterisk server crashes randomly, about once every two
days.
GDB shows random locations for the crash. The only thing they have in
common is that it's something near malloc, but it's being called from
really different locations each time.



====================================================================== 

---------------------------------------------------------------------- 
 (0110747) tilghman (administrator) - 2009-09-15 16:27
 https://issues.asterisk.org/view.php?id=15616#c110747 
---------------------------------------------------------------------- 
Well, there's something that one or more of your agents are doing that is
probably causing this crash (not their fault, ours), and you'll need to
narrow down what that special operation is.  Is it possible to segment out
a section of your call center to run on a debug server, so that this could
be tracked down?

Unfortunately, without knowing your application and what exactly your
agents are doing, it's incredibly difficult to figure out the source of the
memory corruption. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-15 16:27 tilghman       Note Added: 0110747                          
======================================================================