[asterisk-bugs] [Asterisk 0012555]: Crash is sip_destroy

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12555 
====================================================================== 
Reported By:                callguy
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12555
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.19 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 114848 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-30-2008 05:37 CDT
Last Modified:              05-01-2008 06:26 CDT
====================================================================== 
Summary:                    Crash is sip_destroy
Description: 
We upgraded one of our servers to r114848M, and are finding that it crashes
anywhere between every few minutes to few hours. An example backtrace is
attached, but this appears to be related to something in sip_destroy, and
more specifically the update_call_counter function. 

It appears that this may be related to some of the work committed in
r114522, but it's difficult to say for certain. 
====================================================================== 

---------------------------------------------------------------------- 
 callguy - 05-01-08 06:26  
---------------------------------------------------------------------- 
snuffy: that patch didn't make any difference that i can tell. we were
still crashing a couple of times an hour. i grabbed some gdb output:

bt
bt full
thread apply all bt
thread apply all bt full

if there's any other data i can pull please let me know, but this
definitely seems to be a deeper issue than an uninitialized variable. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-01-08 06:26  callguy        Note Added: 0086247                          
======================================================================