[asterisk-bugs] [Asterisk 0010775]: Asterisk suddenly slows down, and eats 100% cpu

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10775 
====================================================================== 
Reported By:                atis
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10775
Category:                   Core-General
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:            1.4.10  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             09-20-2007 16:36 CDT
Last Modified:              09-24-2007 03:44 CDT
====================================================================== 
Summary:                    Asterisk suddenly slows down, and eats 100% cpu
Description: 
I'm running 1.4.10 (with reverted res_features from
http://bugs.digium.com/view.php?id=10415). Approximately
once or twice per week (restarted daily) asterisk suddenly starts acting
slowly, and eats 100% cpu. Call volume drops as it takes really long time
for customers to get to agents, but this doesn't improve situation in any
way.

Last week i recompiled with DONT_OPTIMIZE, DEBUG_THREADS and DEBUG_LOCKS,
so now i can attach debug output.

I killed asterisk with "killall -5 asterisk", so that core is dumped.

Attached files:
backtrace.txt - backtraces taken from core

report.txt - various information ("top", "core show threads", "core show
locks", "core show channels") right before i killed asterisk.

normal.txt - top, and channel count when under normal load (30 minutes
after kill)

cli.txt - multiple consecutive executions of "core show threads" and "core
show locks", when problem raised.


====================================================================== 

---------------------------------------------------------------------- 
 atis - 09-24-07 03:44  
---------------------------------------------------------------------- 
You don't expect me to run that on production, and wait for problem (did i
said that it happens once per week)? It's almost as slow as the problem
itself.

Plus, running valgrind on test machine didn't revealed me anything
happening inside, just some error and leak summaries. I used "sudo valgrind
asterisk -vvvvvdcg". 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
09-24-07 03:44  atis           Note Added: 0071022                          
======================================================================