[Asterisk-bugs] [Asterisk 0010132]: Asterisk Random Segfault (might coincide with parking a call)

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10132 
====================================================================== 
Reported By:                FuriousGeorge
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10132
Category:                   Addons/General
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.6 
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        No 
Request Review:              
====================================================================== 
Date Submitted:             07-06-2007 00:52 CDT
Last Modified:              07-17-2007 11:18 CDT
====================================================================== 
Summary:                    Asterisk Random Segfault (might coincide with
parking a call)
Description: 
Asterisk crashed earlier today and dumped a core.  Examining the backtrace
reveals it was a segfault.  That is about as much as I understand.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0010103 Asterisk Crashes with:   ERROR[13628] /...
====================================================================== 

---------------------------------------------------------------------- 
 FuriousGeorge - 07-17-07 11:18  
---------------------------------------------------------------------- 
UPDATE:
I had an unrelated hardware issue that forced me to restart the server a
few days after upgrading, but I'm happy to report since then I have 7 days
of uptime (which lately is something of an accomplishment at this
location).

Unfortunately, I have no way of knowing if it was the upgrade to 1.4.6 or
the abandoning of our phone's ParkOrbit feature which has at least to some
extent helped our stability.  I'm strongly leaning toward the latter, as I
have other identical servers that never experience this issue, and never or
rarely use ParkOrbit.

If I'm correct about that last part then I assume the issue SHOULD be
resolved, but only time will tell. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-17-07 11:18  FuriousGeorge  Note Added: 0067443                          
======================================================================