Unity's constant whole-screen damaging uses a lot of CPU-cycles and energy, is not efficient and slows rendering down

Bug #1182803 reported by MC Return on 2013-05-22
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Compiz
High
Unassigned
Unity
Confirmed
Undecided
Unassigned

Bug Description

[How to reproduce]

1. Enable the showrepaint plugin in CCSM to be able to observe the damaging
2. Change the clock to show seconds also, or better "sudo apt-get install indicator-multiload"
3. Once indicator-multiload runs, activate showrepaint

[What you would expect to happen]

Unity/Compiz should damage the parts of the screen that are redrawing only, just like the other Compiz plugins do.

[What actually happens]

Unity constantly damages the whole screen, wasting a lot of energy and being completely energy-inefficient.
The problem gets worse if you add additional displays to your configuration.

Workaround:
Disable unityshell.

MC Return (mc-return) on 2013-05-22
description: updated
summary: - Unity's constant whole-screen damaging uses a lot of CPU-cycles, wastes
- a lot of energy and is not efficient
+ Unity's constant whole-screen damaging uses a lot of CPU-cycles and
+ energy, is not efficient and slows rendering down
Leuke (leuke) on 2013-05-23
tags: added: performance
Iven Hsu (ivenvd) wrote :

I'm not using unity, but my screen keeps fullscreen redrawing. How can I see which plugin is causing this problem?

PS: I'm not using the "Workaround" Plugin.

MC Return (mc-return) wrote :

@ivend:
Turn them off one by one, and check the damaging with the "Show Repaint" plugin
 Note that other docks/programs can cause damage events also, so I would recommend also killing other programs drawing on the screen one by one to find the culprit.

B Bobo (yout-bobo123) on 2013-06-17
Changed in unity:
status: New → Confirmed
Changed in compiz:
status: New → Confirmed
MC Return (mc-return) on 2013-06-22
Changed in compiz:
milestone: none → 0.9.10.0
importance: Undecided → High
Changed in compiz:
milestone: 0.9.10.0 → 0.9.10.2
MC Return (mc-return) on 2013-07-24
Changed in compiz:
milestone: 0.9.10.2 → 0.9.11.0
Daniel van Vugt (vanvugt) wrote :

Forgive the confusing jargon, but this is actually bug 1080947.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related blueprints