[asterisk-bugs] [Asterisk 0016452]: [patch] 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:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   16452
Category:                   Core/General
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     acknowledged
Target Version:             Potential Blocker
Asterisk Version:           SVN 
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-21 17:10 CST
====================================================================== 
Summary:                    [patch] 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0115617) tilghman (administrator) - 2009-12-21 17:10
 https://issues.asterisk.org/view.php?id=16452#c115617 
---------------------------------------------------------------------- 
I have uploaded a patch, based upon the output in your valgrind.  What it
looks like is that the SIP session timers are firing after they have been
deallocated, so I've moved the deallocation elsewhere and added a flag so
that it short-circuits the session timers.  Hopefully, that corrects the
crash condition. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-12-21 17:10 tilghman       Note Added: 0115617                          
======================================================================