metacity process uses 100% CPU

Bug #350174 reported by Alex Willmer
52
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Drafting Project
Invalid
Undecided
Unassigned
Metacity
Expired
High
metacity (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: metacity

Ubuntu 9.04 beta, metacity 2.25.144-0ubuntu1
After login, Metacity sometimes uses 100% CPU continuously. It does not occur on every boot and I cannot discern the trigger. I don't believe it's compiz related, as I have desktop effects switched off.

Revision history for this message
Alex Willmer (alex-moreati) wrote :
Revision history for this message
Alex Willmer (alex-moreati) wrote : apport-collect data

Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: metacity 1:2.25.144-0ubuntu1
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_GB.UTF-8
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin mythtv plugdev sambashare vboxusers

Revision history for this message
Alex Willmer (alex-moreati) wrote :
Revision history for this message
tjw (tjw-tjw) wrote :

I have the same issue.

The metacity process that you notice using 100% cpu is not the one you are actually using. It is a process left over from an X11 crash, you can 'kill -9' it.

Not really useful, but here is how I reproduce the X11 crash: Run Half Life 2 in Steam (in wine). Exit the game. X11 backtrace points at the nvidia driver, so nothing Ubuntu can fix there, but more info can be better than not enough I suppose.

Revision history for this message
Pieter (diepes) wrote :

had the same problem, X crashed/restarted during high disk IO, copying to USB flash + USB hd.
After restart cpu 100%, reading comment above i found 2 x metacity and killed one.
That fixed it for me.

$ ps ax | grep meta
 6494 ? RN 112:55 /usr/bin/metacity --replace
17758 ? S 0:01 /usr/bin/metacity --replace
$ kill -quit 6494

Revision history for this message
thewk (theewk) wrote :

I was just about to report this same bug, occurs in Ubuntu 9.04 sometimes. To trigger this no special software has to be used, atleast I haven't noticed.

Changed in metacity (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :
Changed in ubuntu-tn-drafting:
status: New → Invalid
Changed in metacity (Ubuntu):
status: New → Triaged
Revision history for this message
Babar (babarhaq) wrote :

Does this bug have some thing to do with wine/cross-office? I use M$ Outlook heavily 9.04 and see this problem every now and then. Will try to test this further.

Revision history for this message
Alex Willmer (alex-moreati) wrote :

This behavior is not present for me in Lucid, and IIRC wasn't present in 9.10. I don't believe I was not running Wine applications at the time.

Revision history for this message
Alex Willmer (alex-moreati) wrote :

Ugh, engage brain. I don't believe I was running Wine applications at the time.

Revision history for this message
CNBorn (cnborn) wrote :

I have the same issue that causes X restarts (Jaunty). Not running any specific programs that are obviously causing this problem. I have no wine applications installed.

Revision history for this message
dallaylaen (khedin) wrote :

Looks like Alt+SysRq+K can trigger this bug. Can anyone confirm this?

Changed in metacity:
importance: Unknown → High
status: Unknown → New
Revision history for this message
willdeans (william-deans) wrote :

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

Changed in metacity:
status: New → Incomplete
Changed in metacity:
status: Incomplete → Expired
Changed in metacity (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.