Comment 7 for bug 1044060

The problem has not been solved, but I don't think it's compiz that's causing the trouble. Last night I installed gnome: sudo aptitude install gnome. This morning I was running gnome-shell, not compiz/unity, and got gnome-shell using 100% cpu. I ran dstack.sh 5 times for gnome-shell, and definitely got the spike. Every time the spike seemed to have ended, when I started using Google Chrome Browser again, the spike started again.

So, I ran dstack.sh a several more times. Finally, I had to killall gnome-shell and run gnome-shell again. Last night when I was having a different problem with gnome-shell, I tried mutter --replace, but to my surprise, mutter --replace doesn't work with gnome-shell because I didn't have mutter installed! So, does that mean gnome-shell was using compiz? Last night, when I was worried that gnome-shell was running under compiz somehow, I found instructions on the internet to find out what window manager was being used and the result was "Mutter" with a capital "M", but "Mutter --replace" also didn't work since "Mutter" wasn't installed either. So, I installed mutter, but mutter --replace doesn't work because it doesn't load gnome-shell, and same thing happens with compiz --replace.

Anyway, whatever gnome-shell is running under, the 100% CPU problem happens with it just as it did with compiz/unity. I'm attaching gnomestack.txt hoping someone will figure out what package really has a bug in it.