[asterisk-bugs] [Asterisk 0011940]: This crash happenned this morning

noreply at bugs.digium.com noreply at bugs.digium.com
Fri Feb 29 17:31:10 CST 2008


The following issue has been ASSIGNED. 
====================================================================== 
http://bugs.digium.com/view.php?id=11940 
====================================================================== 
Reported By:                falves11
Assigned To:                russell
====================================================================== 
Project:                    Asterisk
Issue ID:                   11940
Category:                   Channels/General
Reproducibility:            sometimes
Severity:                   crash
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 102602 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             02-06-2008 13:16 CST
Last Modified:              02-29-2008 17:30 CST
====================================================================== 
Summary:                    This crash happenned this morning
Description: 
I upgraded my production servers to the current version based on advice
from the the bug marshals regarding a dramatic improvement on memory
issues, but got this crash today.
====================================================================== 

---------------------------------------------------------------------- 
 svnbot - 02-29-08 17:30  
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 105409

U   branches/1.4/main/autoservice.c

------------------------------------------------------------------------
r105409 | russell | 2008-02-29 17:30:48 -0600 (Fri, 29 Feb 2008) | 23
lines

Fix a major bug in autoservice.  There was a race condition in the
handling of
the list of channels in autoservice.  The problem was that it was possible
for
a channel to get removed from autoservice and destroyed, while the
autoservice
was still messing with the channel.  This led to memory corruption, and
caused
crashes.  This explains multiple backtraces I have seen that have
references
to autoservice, but do to the nature of the issue (memory corruption),
could
cause crashes in a number of areas.

(fixes the crash in BE-386)
(closes issue http://bugs.digium.com/view.php?id=11694)
(closes issue http://bugs.digium.com/view.php?id=11940)

The following issues could be related.  If you are the reporter of one of
these,
please update to include this fix and try again.

(potentially fixes issue http://bugs.digium.com/view.php?id=11189)
(potentially fixes issue http://bugs.digium.com/view.php?id=12107)
(potentially fixes issue http://bugs.digium.com/view.php?id=11573)
(potentially fixes issue http://bugs.digium.com/view.php?id=12008)
(potentially fixes issue http://bugs.digium.com/view.php?id=11189)
(potentially fixes issue http://bugs.digium.com/view.php?id=11993)
(potentially fixes issue http://bugs.digium.com/view.php?id=11791)

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=105409 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-29-08 17:30  svnbot         Checkin                                      
02-29-08 17:30  svnbot         Note Added: 0083179                          
02-29-08 17:30  svnbot         Status                   feedback => assigned
02-29-08 17:30  svnbot         Assigned To               => russell         
======================================================================




More information about the asterisk-bugs mailing list