[asterisk-bugs] [Asterisk 0016158]: High CPU usage, choppy sound
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Nov 9 08:19:55 CST 2009
The following issue requires your FEEDBACK.
======================================================================
https://issues.asterisk.org/view.php?id=16158
======================================================================
Reported By: mustardman
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 16158
Category: Channels/chan_sip/General
Reproducibility: random
Severity: major
Priority: normal
Status: feedback
Asterisk Version: 1.6.1.8
JIRA:
Regression: Yes
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-10-30 19:45 CDT
Last Modified: 2009-11-09 08:19 CST
======================================================================
Summary: High CPU usage, choppy sound
Description:
After upgrading from Asterisk 1.6.1.6 to 1.6.1.8 I seem to have a random
problem with high CPU usage. When making a SIP to SIP call or SIP to
System call Asterisk process CPU usage goes much higher than normal and the
sound get's choppy. This is somewhat random but occurs fairly regularly,
maybe 50% of the time.
If it happens it happens as soon as a call is answered. CPU usage
sometimes stays high for minutes and will suddenly go low even though I
didn't do anything. More often than not it only stays high for a short
period of time and then goes back to normal.
I am running 64bit CentOS 5.4. Log files and Asterisk CLI -vvvvvvvvvvr
look clean.
Not sure if this is useful but I will attached a gdb.txt file taken while
it is happening
======================================================================
----------------------------------------------------------------------
(0113404) lmadsen (administrator) - 2009-11-09 08:19
https://issues.asterisk.org/view.php?id=16158#c113404
----------------------------------------------------------------------
The difference between 1.6.1.x and 1.6.2.x is a major version change --
they cannot be compared to each other.
You have still not answered the initial question of whether just running
1.6.1.6 continues to have the same problem as 1.6.1.8 was only a security
update which did not touch this part of the code.
Additionally, 1.6.1.9 was also only a security update which should not
have affected this.
1.6.1.10-rc1 would be a more appropriate version to check against as bug
fixes will be contained in there beyond 1.6.1.6.
I would like to see if 1.6.1.6 is experiencing this same issue, as I don't
see how the update to 1.6.1.8 could have alone explained this issue.
Issue History
Date Modified Username Field Change
======================================================================
2009-11-09 08:19 lmadsen Note Added: 0113404
2009-11-09 08:19 lmadsen Status new => feedback
======================================================================
More information about the asterisk-bugs
mailing list