[asterisk-bugs] [Asterisk 0013179]: Irrelevant Notice

Asterisk Bug Tracker noreply at bugs.digium.com
Mon Jul 28 10:47:33 CDT 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13179 
====================================================================== 
Reported By:                leobrown
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13179
Category:                   Core/Channels
Reproducibility:            random
Severity:                   tweak
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.23 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-07-28 09:40 CDT
Last Modified:              2008-07-28 10:47 CDT
====================================================================== 
Summary:                    Irrelevant Notice
Description: 
The message "Attempted to delete nonexistent schedule entry" from sched.c
occurs in 1.4.0 upwards on a frequent basis at cleardown time. This
detracts from the use of Log/Verbose applications to provide meaningful
warnings to the console.
====================================================================== 

---------------------------------------------------------------------- 
 (0090757) Corydon76 (administrator) - 2008-07-28 10:47
 http://bugs.digium.com/view.php?id=13179#c90757 
---------------------------------------------------------------------- 
It's not actually irrelevant.  Being unable to delete a schedule entry is
actually a potential source of a crash or alternately, a memory leak.  If
the scheduler fires after you deallocate the memory associated with that
task, it could result in memory corruption and a crash.  If you fail to
deallocate that memory, your process may leak memory. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-07-28 10:47 Corydon76      Note Added: 0090757                          
======================================================================




More information about the asterisk-bugs mailing list