Poor performance with Compiz scale plugin: lag when showing windows

[Ethan Hogue]

What was expected:
-smooth transition to the window overwies when clicking a launcher icon with more than one window open, or when using the super+w shortcut to show all windows on the workspace.

What happened instead:
-there was considerable lag when displaying the windows: stuttering and stalling occurred.

Possible causes:
1) the fade in/out of other visible windows when opening the overview (only applies to clicking launcher icon);
2) the new "close window/window title" addon is initializing at the wrong time/place, causing unnecessary gpu/cpu load.

This issue was not present in Precise, ie before the new close button plugin, but I now experience it in Quantal
One of the most common occurrances is that the windows pause halfway through the animation for about 1/8 of a second before continuing the animation.
Another is that the launcher click to spread windows animation pauses about 1/4 of the way through for about 1/8 of a second before continuing. While the animation is lagging I can see the partly-faded windows in the background.

If I new where/how to start I'd look at the code for the new window title/close button plugin and try to figure out why it might be causing lag. I'm not entirely sure, but I think that it may be being called too early.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: compiz 1:0.9.8.4+bzr3407-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:

ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
Date: Fri Nov 16 17:20:51 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus: bcmwl, 5.100.82.112+bdcom, 3.5.0-18-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:043f]
InstallationDate: Installed on 2012-11-13 (2 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: Acer TravelMate 8372
MarkForUpload: True
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-18-generic root=UUID=2ab95791-9cc1-4555-97f4-e0bae9ae854f ro quiet splash vt.handoff=7
SourcePackage: compiz
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/14/2010
dmi.bios.vendor: Acer
dmi.bios.version: V1.07
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: TravelMate 8372
dmi.board.vendor: Acer
dmi.board.version: PSMBOU-1234567
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: None
dmi.modalias: dmi:bvnAcer:bvrV1.07:bd12/14/2010:svnAcer:pnTravelMate8372:pvrV1.07:rvnAcer:rnTravelMate8372:rvrPSMBOU-1234567:cvnAcer:ct10:cvrNone:
dmi.product.name: TravelMate 8372
dmi.product.version: V1.07
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.39-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1039942, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.