[asterisk-bugs] [Asterisk 0015845]: Crash during attended transfer occurs

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Oct 8 14:49:24 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15845 
====================================================================== 
Reported By:                marhbere
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15845
Category:                   Resources/res_musiconhold
Reproducibility:            sometimes
Severity:                   crash
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.0 
SVN Revision (number only!): 215420 
Request Review:              
====================================================================== 
Date Submitted:             2009-09-07 15:11 CDT
Last Modified:              2009-10-08 14:49 CDT
====================================================================== 
Summary:                    Crash during attended transfer occurs
Description: 
related view.php?id=15460 we haven´t any change after the patched.

Now run Asterisk SVN-branch-1.6.0-r215420M
and Asteris-Addons 1.6.0 r1024

Remembering: We are using queue's with SIP static and dynamic members; mho
based in File from mp3.
I will attach new GDB, pls tell me if you need something more.


======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
duplicate of        0015962 Asterisk crashed after transfer
related to          0015460 Asterisk Crashed When made a attended T...
related to          0015109 [patch] Abort by memory allocator, poss...
related to          0015841 [patch] double free or corruption (!pre...
related to          0015609 [patch] WARNING[23025]: channel.c:952 _...
related to          0015817 crash in local_attended_transfer, likel...
====================================================================== 

---------------------------------------------------------------------- 
 (0112067) svnbot (reporter) - 2009-10-08 14:49
 https://issues.asterisk.org/view.php?id=15845#c112067 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 222878

U   branches/1.4/include/asterisk/file.h
U   branches/1.4/include/asterisk/frame.h
U   branches/1.4/main/file.c
U   branches/1.4/main/frame.c

------------------------------------------------------------------------
r222878 | russell | 2009-10-08 14:49:10 -0500 (Thu, 08 Oct 2009) | 44
lines

Make filestream frame handling safer by isolating frames before returning
them.

This patch is related to a number of issues on the bug tracker that show
crashes related to freeing frames that came from a filestream.  A number
of
fixes have been made over time while trying to figure out these problems,
but
there re still people seeing the crash.  (Note that some of these bug
reports
include information about other problems.  I am specifically addressing
the filestream frame crash here.)

I'm still not clear on what the exact problem is.  However, what is _very_
clear is that we have seen quite a few problems over time related to
unexpected
behavior when we try to use embedded frames as an optimization.  In some
cases,
this optimization doesn't really provide much due to improvements made in
other
areas.

In this case, the patch modifies filestream handling such that the
embedded frame
will not be returned.  ast_frisolate() is used to ensure that we end up
with a
completely mallocd frame.  In reality, though, we will not actually have
to malloc
every time.  For filestreams, the frame will almost always be allocated
and freed
in the same thread.  That means that the thread local frame cache will be
used.
So, going this route doesn't hurt.

With this patch in place, some people have reported success in not seeing
the
crash anymore.

(SWP-150)
(AST-208)
(ABE-1834)

(issue https://issues.asterisk.org/view.php?id=15609)
Reported by: aragon
Patches:
      filestream_frisolate-1.4.diff2.txt uploaded by russell (license 2)
Tested by: aragon, russell

(closes issue https://issues.asterisk.org/view.php?id=15817)
Reported by: zerohalo
Tested by: zerohalo

(closes issue https://issues.asterisk.org/view.php?id=15845)
Reported by: marhbere

Review: https://reviewboard.asterisk.org/r/386/

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

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

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-08 14:49 svnbot         Checkin                                      
2009-10-08 14:49 svnbot         Note Added: 0112067                          
======================================================================




More information about the asterisk-bugs mailing list