[asterisk-bugs] [Asterisk 0016041]: Asterisk 1.4.27-rc2 crash

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16041 
====================================================================== 
Reported By:                francesco_r
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16041
Category:                   Channels/chan_misdn
Reproducibility:            random
Severity:                   block
Priority:                   normal
Status:                     feedback
Target Version:             1.4.27
Asterisk Version:           1.4.27-rc2 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-10-08 04:12 CDT
Last Modified:              2009-10-12 09:29 CDT
====================================================================== 
Summary:                    Asterisk 1.4.27-rc2 crash
Description: 
I have many crash since i have upgraded to Asterisk 1.4.27-rc2. Attached a
full bt.
====================================================================== 

---------------------------------------------------------------------- 
 (0112202) sodom (reporter) - 2009-10-12 09:29
 https://issues.asterisk.org/view.php?id=16041#c112202 
---------------------------------------------------------------------- 
Hmm,

that's the same i monitor.. mostly our pbx went down after i power it on
(It didn't run the whool day) and it need to handle the first calls. I'am
still not able to change the system to debug mode and my test system didn't
generate the problem in the moment. (We run a 1.4.26er system)
As i noted in my bug report i think it's the hangup process. In the moment
i think it's an access to channel elements already freed priviously in the
hang process but maybe i misinterpret the situation. (Sorry for not
offerening hard facts.) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-12 09:29 sodom          Note Added: 0112202                          
======================================================================