|Summary:||ASTERISK-12469: Irrelevant Notice|
|Reporter:||Leo Brown (netfuse)||Labels:|
|Date Opened:||2008-07-28 09:40:17||Date Closed:||2011-06-07 14:07:50|
|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.|
|Comments:||By: Tilghman Lesher (tilghman) 2008-07-28 10:47:32|
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.
By: Leo Brown (netfuse) 2008-07-28 10:53:33
In which case, 1.4.0, which is currently running and stable on four identical servers puts these messages out 1 in 5 calls. Memory usage is stable and we havent had any dropped calls/crashes since using this version over a month ago. What further info would be useful?
By: Tilghman Lesher (tilghman) 2008-07-28 11:14:24
1.4.0 is a REALLY old release. I'm frankly surprised that you would have no memory corruption or issues on that version.
By: Leo Brown (netfuse) 2008-07-28 11:22:32
Good point. But we only moved to 1.4.0 due to memory corruption and stability issues, such as found in 1.4.7 through 1.4.21. I think this one was hitting us http://bugs.digium.com/view.php?id=13160. Anyway, we'll continue to monitor the problem and if we experience any memory issues we'll change versions.