[asterisk-bugs] [Asterisk 0016801]: problems with high call frequency and more than 300 calls at the same time

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16801 
====================================================================== 
Reported By:                marco_wc
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16801
Category:                   Channels/General
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.2.2 
JIRA:                       SWP-1088 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-02-10 08:38 CST
Last Modified:              2010-04-29 02:10 CDT
====================================================================== 
Summary:                    problems with high call frequency and more than 300
calls at the same time
Description: 
asterisk-1.4.29 works without problem i have test with 480 Calls


what traces do you need ?

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

---------------------------------------------------------------------- 
 (0121146) davidw (reporter) - 2010-04-29 02:10
 https://issues.asterisk.org/view.php?id=16801#c121146 
---------------------------------------------------------------------- 
No-one seems to have noticed the most serious error message here:

*** glibc detected *** asterisk: munmap_chunk(): invalid pointer:
0x0894ca08 ***

Looks like there is memory corruption.  With the caveat that it can
sometimes make the system run too slowly even to do the test, I believe the
debugging protocol requires the use of the procedure in doc/valgrind.txt,
at this point.

(The abort, rather than segmentation fault, in the last backtrace, also
tells you that you are dealing with some sort of memory management problem 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-29 02:10 davidw         Note Added: 0121146                          
======================================================================