[asterisk-bugs] [Asterisk 0017063]: CPU usage increases if WaitEvent not called
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Mar 22 14:24:05 CDT 2010
The following issue has been UPDATED.
======================================================================
https://issues.asterisk.org/view.php?id=17063
======================================================================
Reported By: timking
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17063
Category: Core/HTTP
Reproducibility: always
Severity: minor
Priority: normal
Status: acknowledged
Asterisk Version: 1.6.0.26
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-03-20 08:33 CDT
Last Modified: 2010-03-22 14:24 CDT
======================================================================
Summary: CPU usage increases if WaitEvent not called
Description:
If someone logs in via the mxml interface with reporting rights then all
events are buffered until they log out (or timeout) or call WaitEvent. If
the timeout is long and/or they issue other commands regularly such as
Status - but crucially not WaitEvent - then Asterisk starts to consume RAM
and significant CPU. The RAM usage is obvious but I don't see why having
10,000 events waiting in the queue should cause increased CPU, although
giving the command
manager show eventq
in this case did cause asterisk to drop all current calls. Timeouts while
list is locked I assume.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2010-03-22 14:24 lmadsen Description Updated
======================================================================
More information about the asterisk-bugs
mailing list