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

noreply at bugs.digium.com noreply at bugs.digium.com
Tue Feb 19 23:57:45 CST 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11940 
====================================================================== 
Reported By:                falves11
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11940
Category:                   Channels/General
Reproducibility:            sometimes
Severity:                   crash
Priority:                   normal
Status:                     feedback
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-19-2008 23:57 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.
====================================================================== 

---------------------------------------------------------------------- 
 norman - 02-19-08 23:57  
---------------------------------------------------------------------- 
I had another similar crash after installing the 11960 patch as well.
Perhaps there are multiple crashes. I'm using ODBC as well, perhaps that's
the problem? What ODBC driver are you using? Looks like FreeTDS, which I'm
also using.

I ran my test under valgrind, and valgrind didn't find anything yet after
using 200 threads it crashed and reported a corrupt stack trace just like
in this latest blow up. So, at least in my case, valgrind can't find it.

Do you use IAX? My crashed thread was in the middle of several IAX
threads. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-19-08 23:57  norman         Note Added: 0082621                          
======================================================================




More information about the asterisk-bugs mailing list