[asterisk-bugs] [Asterisk 0016452]: Lots of crashes after upgrading to latest 1.6.0.20-rc1

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16452 
====================================================================== 
Reported By:                corruptor
Assigned To:                dvossel
====================================================================== 
Project:                    Asterisk
Issue ID:                   16452
Category:                   Core/General
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.6.0.20-rc1 
JIRA:                       SWP-551 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-12-16 04:23 CST
Last Modified:              2009-12-16 10:56 CST
====================================================================== 
Summary:                    Lots of crashes after upgrading to latest
1.6.0.20-rc1
Description: 
I've tried to upgrade my asterisk 1.6.19 to latest RC. Asterisk crashes
every 30-40 minutes. There are about 15 concurrent calls. All calls are
recorded using MixMonitor. Asterisk crashes after hanging up one of the
calls.
I upload the backtrace.
Asterisk 1.6.19 same config works ok.
====================================================================== 

---------------------------------------------------------------------- 
 (0115330) russell (administrator) - 2009-12-16 10:56
 https://issues.asterisk.org/view.php?id=16452#c115330 
---------------------------------------------------------------------- 
Your backtraces are very different.  It sort of looks like an invalid
channel is being accessed and has resulted in two different crashes.  It's
hard to know.  We're going to try to do a bit of testing with the
information we have, but we will most likely need more information from you
to address this.

Some analysis using valgrind would be very useful.  See the instructions
in doc/valgrind.txt.  However, note that this will introduce a lot of extra
load on your system, so it may not be able to handle your full load while
doing this testing. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-12-16 10:56 russell        Note Added: 0115330                          
======================================================================