[asterisk-bugs] [Asterisk 0012308]: high SIP call volume locks Asterisk 1.4.19rc3

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12308 
====================================================================== 
Reported By:                mflorell
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12308
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.19-rc3 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             03-26-2008 11:23 CDT
Last Modified:              03-26-2008 12:30 CDT
====================================================================== 
Summary:                    high SIP call volume locks Asterisk 1.4.19rc3
Description: 
I am able to reliably lock up Asterisk and send the loadavg on the server
to 100.00 and higher within 5 minutes of starting performance testing with
300+ channels(all SIP). With IAX, even at higher call volumes, it does not
crash at all.

Here is a link to the 20,000+ line GDB output:
http://www.eflo.net/files/Asterisk_1.4.19rc3_crash_gdb_2008-03-26.txt

I tried doing a "core show threads" but Asterisk was not responding.


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

---------------------------------------------------------------------- 
 junky - 03-26-08 12:30  
---------------------------------------------------------------------- 
Could you recompile * with DONT_OPTIMIZE compiler flag?
Since we're seeing a lot of <value optimized out>, which is not really
revelent.


Also, include that:
frame 1
p *rtp
p *rtp->rtcp 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-26-08 12:30  junky          Note Added: 0084588                          
======================================================================