Red Hat Bugzilla – Bug 418571
mixer_applet2 using 99% CPU
Last modified: 2010-07-28 22:12:59 EDT
Description of problem:
mixer_applet2 is using 99-100% of the cpu on my system until I restart it
(restart the applet, that is):
top - 12:04:44 up 20 days, 18:51, 30 users, load average: 5.09, 2.60, 1.83
Tasks: 269 total, 1 running, 265 sleeping, 2 stopped, 1 zombie
Cpu(s): 29.9%us, 27.0%sy, 0.0%ni, 4.5%id, 36.2%wa, 0.6%hi, 1.8%si, 0.0%st
Mem: 1026908k total, 1016616k used, 10292k free, 44k buffers
Swap: 2048276k total, 633516k used, 1414760k free, 102300k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
17955 esandeen 20 0 310m 7136 5524 S 100 0.7 4009:55 mixer_applet2
2855 root 20 0 188m 65m 7456 S 5 6.6 89:31.16 X
8897 root 20 0 374m 162m 6256 D 2 16.2 0:05.96 yum
471 root 20 0 0 0 0 S 2 0.0 1:47.78 nfsd
Version-Release number of selected component (if applicable):
Run mixer_applet2 & wait, I guess...
[root@neon linux-2.6.24-rc3]# ps ax | grep mixer
17955 ? Sl 4011:14 /usr/libexec/mixer_applet2
[root@neon linux-2.6.24-rc3]# strace -p 17955
Process 17955 attached - interrupt to quit
read(3, 0x635404, 4096) = -1 EAGAIN (Resource temporarily
[root@neon linux-2.6.24-rc3]# ls -l /proc/17955/fd/3
lrwx------ 1 esandeen esandeen 64 2007-12-10 12:09 /proc/17955/fd/3 ->
if that helps at all...
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
I am seeing ridiculously high CPU usage by mixer_applet2 starting with a clean install of x86_64 F10. It didn't happen on i386 F9. For example, it uses up over 70% of the CPU while playing a DVD with vlc (with vlc and related processes taking up most of the rest). Please update the Version to 10.
Well, I am seeing this problem in Fedora 10 after resuming from suspend to ram. Logging out and then log back in solves it.
Reporter, can you confirm this? maybe it's the same issue I am seeing here.
I have no f10 boxes with sound yet, so can't confirm myself :)
*** Bug 476354 has been marked as a duplicate of this bug. ***
I still see this on F10. No suspend involved.
I see this after suspend -- during suspend I unplugged an external USB soundcard.
The applet itself seems to be functional though.
this has been reported at http://bugzilla.gnome.org/show_bug.cgi?id=519388
the patch is supposed to be at http://bugzilla.gnome.org/attachment.cgi?id=89596&action=view but a slightly modified version was commited according to http://bugzilla.gnome.org/show_bug.cgi?id=167606#c10
I'm seeing mixer_applet2 consume all of a CPU on both F9 and F10. On neither of these machines am I using a USB soundcard nor am I using suspend.
I've just started seeing this in the last month or so; so I think some update has broadened the impact of this bug.
I haven't seen this bug for a while?? can you reproduce this with F11?
mixer_applet2 isn't part of gnome-applets in F11.
I have not seen this on F11.
Let's go ahead and close this out now.
Just a comment. I ran accross this on RHEL5 with VMWare workstation 6.5.4.
mixer_applet2 CPU went through the roof.
Occurred while booting new VM and workstation was detecting audio devices on vm boot.
So steps to reproduce may be
Run mixer_applet2 & and boot VM
Run mixer_applet2 & wait
It may be a race condition and caused by any number of other audio related apps too.
just killed process and it requested auto start just as above.
Perhaps somebody wants to implement a watchdog to do this automatically and log it when it occurs?