Windows unresponsive and high CPU usage

[Gem]

Binary package hint: compiz

While running compiz with either gtk window decorator, or emerald, windows are slow and unresponsive. A lot of cpu cycles seem to be getting used. Only problem I've had with compiz and other 3D compositing so far is the nvidia driver related memory leak, but this is different as it renders the environment unusable. Using metacity everything runs smoothly.
Nvidia GeForce 6200 TurboCache(TM), driver version 169.12, installed using envyNG. Twinview is also running.
Description: Ubuntu hardy (development branch)
Release: 8.04
compiz 1:0.7.2-0ubuntu2

[Nicolas Joyard (joyard-nicolas)]

I can confirm this bug, however as some elements differ I'm not sure it is the same.
I have a Sony Vaio VGN-FS415S laptop with a GeForce GO 6400 inside. I also have drivers version 169.12 and I'm also using TwinView, but I installed them with jockey (formerly restricted-drivers-manager).

With kernel 2.6.24-12-generic compiz was running fine. With 2.6.24-15-generic running compiz makes the desktop unusable.

[Nicolas Joyard (joyard-nicolas)]

Forgot to mention that nvidia-glx-new was also updated at the same time the kernel was. Therefore it's likely to be more linux-generic- or nvidia-related than compiz-.

[Simone Tolotti (simontol)]

I have a same problem after upgrading to kernel 2.6.24-16, compiz 0.7.4-0ubuntu4
When I rotate the cube and select a workspace the desktop fail to set the correct screen size/resolution. Clicking on the desktop refresh small areas around mouse pointer.
Attached a screenshot.

[Rodrigo Donado (frezeeer)]

Same slow response, again nvidia version 169.12 (with envyNG) and twinview.
it is imposible to use the system

[David Terei (davidterei)]

Same very slow response (unusable). Nvidia 8600GT, Dell XPS M1530 Laptop.

nvidia-glx-new 169.12
kernel 2.6.24.12-16.34

[Rodrigo Donado (frezeeer)]

Hi:

I found a workaround, at least it works for me:
1) Install compizconfig-settings-manager
                  sudo apt-get install compizconfig-settings-manager
2) run it
                  System -> Preferences -> Advanced Desktop Effects Settings
3) then unselect Fading Windows

it should go back to normal.

hope it helps

[Gem (poopshoes)]

Unfortunately Rodrigos workaround doesn't work for me.

[Simone Tolotti (simontol)]

@Rodrigo,Gem: Decreasing the number of active effects could increase compiz performance, but is only a workaround.
I think that the bug is related to nvidia drivers 'cause we all have nvidia cards. I have to mantion that this never happened on Gutsy or Feisty with the same machine.
Nvidia 7300LE
nvidia-glx-new 169.12
Attached glxinfo.

[JofArnold (j-arnold)]

Me too! There's a bunch of bug reports about this focussing on FF3 and other apps being slow, but it looks to me like a gfx driver (I'm no expert - it's just that I experienced identical issues with a bad ati driver before).

Spec: Dell M4300, 9500 intel (2.6Ghz), 4GB ram, nVidia 360M (256mb gfx ram). Thank god for my fast CPU or the system would be unusable. Comparing it to my old laptop - which is about 10x slower - I'd say the performance hit is between 10 and 20x :-| Although removing desktop effects does help, I still have the issue even when running gtk/metacity so that rules out compiz/emerald imho.

[JofArnold (j-arnold)]

Sorry. I double-checked and I was in fact still running compiz. I can confirm that the system is MUCH faster running metacity: FF2 is at full speed as far as I can tell. However, FF3 is still slow - especially at canvas. I don't believe this affects the diagnosis, but it's good to get the facts right ;-)

[JofArnold (j-arnold)]

Just noticed this in /var/log/Xorg.0.log:

(WW) NVIDIA(0): UBB is incompatible with the Composite extension. Disabling
(WW) NVIDIA(0): UBB.

UBB is the back buffer - surely disabling that would give a performance hit?

[Gem (poopshoes)]

Well, I have to say, after the latest round of updates, mine is back to normal. In that lovely works but has a memory leak kinda way. Woo! Though, I've yet to try it with the latest kernel. That doesn't work for me, but that's another bug report...

[Vitaly (vbabiy86)]

I am also having this issues I am on a Dell m1530.

nVidia Corporation GeForce 8600M GT, Driver version 169.12

With all the updates.

[bayer (daniel-reichhard)]

i can confirm rogrigos observation:

selecting "fading windows" will cause the compiz.real process to consume 60%+ cpu time, unchecking it solves the problem!

[vennec (vennec)]

Same issue for me.
Since I've been upgrading to Hardy, compiz desktop effects are very slow, quite unusable sometimes...
With glxgears, i only get 400 FPS.
(Previously with the same hardware on Feisty Fawn I had 3200 FPS!!!)
My graphic card is a GeForce 6200.
I use the 169.12 binary driver, I tried with envy, but with no success.
I didn't modify my xorg.conf and didn't notice any weird things in my logs...

[Spenser Bauman (sabauma-comcast)]

I have been having the same problem for my laptop. Dell Inspiron 1520 with an NVIDIA 8600GT graphics card.
All the 3D effects work fine, but when opening/closing windows or maximizing/minimizing it is extremely slow.
Also, the buttons for closing maximizing and minimizing have been slow to respond.

I believe I have either solved or worked around the problem though.
My system began functioning very except for two of the window animations when I installed the xserver-xgl package.
The two slow effects were the flame and beam up effects; they seem to be working a little better now thanks to Rodrigo Donado by disabling the Fading Windows effect.

WARNING: after enabling the xserver-xgl package, I have been unable to use the built in screen resolution utility and the glow around the windows disappeared.

[JofArnold (j-arnold)]

At least 90% of it appears to be due to NVIDIA:

e.g.: http://www.nvnews.net/vbulletin/showthread.php?t=112612

In one of the threads elsewhere on that forum an NVIDIA representative admits there's a problem and that it will be fixed "soon". By "soon" I wouldn't be surprised if he/she means "in the next 2-3 months", so I guess we'll all have to play a waiting game and disable compiz for now :-S

[tetsuo (dtab1064)]

makes meh sad :(

[JofArnold (j-arnold)]

Makes me sad too... so sad I'm going to try OSX for a month and possibly move to that. Until NVIDIA gets their act together, I've tried the following with various degrees of success:

My fix
-------
sudo apt-get install xserver-xgl

This works way better than any other solution for me, however xgl doesn't work with all nvidia drivers (ok with the nvidia-glx-new 169.12 for me). XGL has some weird minor side-effects too, but mostly good for me. 110fps versus 10fps with proper driver is an improvement!

Proper way
----------
VSYNC:
Appending the "Option "DynamicTwinView" "false"" to my xorg / device section, I now get a muuuch smoother experience.

SHADOWS:
official driver
or
sudo ln -s /usr/lib/nvidia/libwfb.so.xserver-xorg-core /usr/lib/xorg/modules/libwfb.so

OVERCLOCKING:
1) open /etc/modprobe.conf
2) add the lines:
options nvidia NVreg_RegistryDwords="PerfLevelSrc=0x2222"
 OR options nvidia NVreg_RegistryDwords="PerfLevelSrc=0x3322"
options nvidia NVreg_Mobile=1
3) Reboot

PIXMAPCACHESIZE
 Section "Screen"
 ........
 Option "PixmapCacheSize" "200000"
 ........
 EndSection

[subru77 (subru77)]

I have the same problem. Compiz was faster in Gutsy. It was faster when I upgraded from Gutsy.
Since I did a fresh install of Hardy, Compiz is dead slow.. UI is dragging. :(

[subru77 (subru77)]

I was able to get better performance with installing EnvyNG and then script mentioned in the below link.
http://ubuntuforums.org/showthread.php?p=5181027&mode=linear#post5181027

[Bryce Harrington (bryce)]

Thank you for reporting this issue about a driver from the
linux-restricted-modules package. lrm-2.4.24 was shipped with Ubuntu
8.04 which reached end-of-life for desktop support on May 12th, 2011.

For that reason, this bug report is being closed at this time. I'm
marking it wontfix because what you describe is probably a valid issue,
but there are no plans to work on lrm 2.4.24 bugs further.

The issue may be resolved in a newer version. If not, aside from filing
a new bug report, another angle may be to file it directly with the
driver vendor.