[asterisk-bugs] [Asterisk 0015665]: Asterisk eats up all the processor and prints the same message in the screen

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15665 
====================================================================== 
Reported By:                falves11
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15665
Category:                   Channels/chan_sip/General
Reproducibility:            random
Severity:                   block
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.26 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!): 99999 
Request Review:              
====================================================================== 
Date Submitted:             2009-08-06 00:19 CDT
Last Modified:              2009-08-16 14:24 CDT
====================================================================== 
Summary:                    Asterisk eats up all the processor and prints the
same message in the screen
Description: 
[Aug  6 00:17:21] ERROR[71296]: channel.c:2522 __ast_read: ast_read()
called with no recorded file descriptor.
====================================================================== 

---------------------------------------------------------------------- 
 (0109086) falves11 (reporter) - 2009-08-16 14:24
 https://issues.asterisk.org/view.php?id=15665#c109086 
---------------------------------------------------------------------- 
The issue happens with 1.6.2, not with 1.4. The Business Edition support
told me that they fixed this bug in the new release, but obviously they did
not update the 1.6 branch. Asterisk simply goes in a look and eats up one
processor. This is random. If Asterisk is not rebooted soon another thread
gets in the loop and eats more than one processor, etc. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-16 14:24 falves11       Note Added: 0109086                          
======================================================================