For me metacity uses 100% CPU because "Wireless Network Authentication Required" boxes appear every "few minutes?" and never go away (unless manually closed). Eventually there are hundreds? of them and metacity uses 100% CPU dealing with them.
You might not notice them if they appear on a different virtual desktop than the one you are using or if the bar showing your currently running applications is hidden or if the number of windows is so large they only appear a few pixels wide in the "task bar" or if you accessing your system via ssh or any other such reason. In my mind this is a metacity bug but I am sure others would argue with me that what I want is a feature enhancement. Why doesn't metacity restrict its CPU utilization on a per-client bases so that a single misbehaving application cannot bring down the system? Misbehaving applications are AN EXPECTED behavior. If there was some [high] burstable quota this wouldn't be an issue. If the quota is met and the application is throttled an indicator applet could allow the user to change/remove the quota for the application. cat /etc/issue Ubuntu 12.04.2 LTS \n \l -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/350174 Title: metacity process uses 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/350174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
