Week 32: Number of wakeups per second for compiz is more than 50

Bug #1034055 reported by Nice Testhouse
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Compiz
Incomplete
Medium
Unassigned
The Ubuntu Power Consumption Project
Expired
Undecided
Unassigned
compiz (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

It appears the mousepoll plugin timer sometimes gets stuck on, and keeps polling when it probably should not any more.

See also: bug 961202

ORIGINAL DESCRIPTION:
Week 32: Ubuntu 12.10 Quantal (Radeon) with ppa:unity-team/staging
Test Case ID: Can 35
Failure reason: The number of wakeups per second (events per second) reported for the compiz process is 62.

Follow the below steps:
#. Ensure the screen is idle, with very little changing.
#. Open a terminal and start a tool that can measure process wakeups per
   second. You can choose one of:
     - gnome-power-statistics (click on Processor)
     - powertop
     - eventstat
#. Hover the mouse pointer over the top end of the Launcher. That's just above
   the Ubuntu icon.
#. Hover the mouse pointer over the bottom end of the Launcher. That's over
   the bottom of the trash icon.
#. Move the mouse pointer back to the centre of the screen and leave it there.
#. Wait 30-60 seconds, leaving the screen idle before verifying the Outcome.

Expected Result:
The number of wakeups per second (events per second) reported for the compiz process should be much lower than 50.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: unity 6.0.0+bzr2538ubuntu0+746 [origin: LP-PPA-unity-team-staging]
ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0
Uname: Linux 3.5.0-8-generic i686
ApportVersion: 2.4-0ubuntu6
Architecture: i386
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CrashDB: unity
Date: Tue Aug 7 17:34:49 2012
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120713.1)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Nice Testhouse (testhouse) wrote :
Revision history for this message
Omer Akram (om26er) wrote :

with the test case I see 85-90 wakeups here.

Changed in compiz:
importance: Undecided → Medium
Changed in unity:
importance: Undecided → Medium
Changed in compiz:
status: New → Confirmed
Changed in unity:
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Sounds like a regression to me :(

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I can't reproduce the bug with the current official unity/compiz for quantal:
    unity 6.0.0-0ubuntu6
    compiz 1:0.9.8+bzr3249-0ubuntu2
And I really should be able to. I wrote the testcase in question.

If you remove the PPA does the bug go away?

Changed in compiz:
status: Confirmed → Incomplete
Changed in unity:
status: Confirmed → Incomplete
Revision history for this message
Omer Akram (om26er) wrote :

In Quantal I am seeing as high as 200 wakeups with this test case with no other activity at all. in 12.04 those wakes are under 50 like 26/s

Revision history for this message
Omer Akram (om26er) wrote :

@I have the exact same packages in Quantal

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Omer, did you follow the last two steps exactly?
#. Move the mouse pointer back to the centre of the screen and leave it there.
#. Wait 30-60 seconds, leaving the screen idle before verifying the Outcome.

Also...
1. What tool and refresh interval are you using to measure wakeups?
2. Any special indicators?
3. Does the same happen in Gnome Classic? (effects provided by compiz, but no Unity)

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

All, please also try:
CCSM > Utility > Mouse position polling > Mouse Poll Interval = MAXIMUM
and then redo the test case.

I suspect there are some cases where the mouse poll timer stays running when it should not.

See also: bug 961202.

Revision history for this message
Omer Akram (om26er) wrote :

I am using powertop. I ended up reinstallig Quantal yesterday and now today I am not able to reproduce the issue on a fresh install. I am not sure what got into all this that day. today powertop shows me a max wakeups for 30 after the steps of the test cases. After a bit more wait of that wakeups go as low as 10.

So for me its not an issue anymore. Though what I am sure of is when I confirmed the issue I was using both unity and compiz from the respository + had executed unity --reset as well just to be sure if any of my config was playing the part.

Revision history for this message
Nice Testhouse (testhouse) wrote :

Week 33 - Same issue observed on Ubuntu 12.10 Quantal with ppa:timo-jyrinki/prerelease on machine with Nvidia card

With default mouse position polling which was set to 10, the wakeups per second for compiz is 66.6

Changed mouse position polling to 100, the resulting wakeups per second for compiz ranges between 11.1 and 9.2

Changed mouse position polling back to 10, this time wakeups per second was around 30 which is acceptable.

Please note that on 2 other machines with Radeon and Intel card, default mouse polling is set to 10 and there is not issue with wakeups per second for compiz process.

Changed in unity:
status: Incomplete → Invalid
Changed in compiz:
status: Incomplete → Confirmed
milestone: none → 0.9.8.0
description: updated
Changed in compiz (Ubuntu):
status: New → Confirmed
Omer Akram (om26er)
no longer affects: unity
Changed in compiz:
milestone: 0.9.8.0 → 0.9.8.1
Changed in compiz:
milestone: 0.9.8.2 → 0.9.8.4
Changed in compiz:
milestone: 0.9.8.4 → 0.9.9.0
Changed in compiz:
milestone: 0.9.9.0 → 0.9.9.2
Changed in compiz:
milestone: 0.9.9.2 → 0.9.10.0
MC Return (mc-return)
Changed in compiz:
milestone: 0.9.10.0 → 0.9.11.0
Revision history for this message
Andrea Azzarone (azzar1) wrote :

Can you still reproduce the issue?

Changed in compiz:
status: Confirmed → Incomplete
Changed in ubuntu-power-consumption:
status: New → Incomplete
Changed in compiz (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for compiz (Ubuntu) because there has been no activity for 60 days.]

Changed in compiz (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for The Ubuntu Power Consumption Project because there has been no activity for 60 days.]

Changed in ubuntu-power-consumption:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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