compiz takes >100% of processor

Asked by SoloTurn

ubuntu-14.10 makes compiz take >100% processor time. what does this mean and how can one get it back to normal?

* hardwareinfo: http://www.ubuntu.com/certification/hardware/201102-7326/components/
* rendering
$ glxinfo | grep rendering
direct rendering: Yes

rt@rt:~$ top

top - 07:39:49 up 11:03, 2 users, load average: 1.35, 1.41, 2.39
Tasks: 203 total, 1 running, 202 sleeping, 0 stopped, 0 zombie
%Cpu(s): 21.7 us, 5.7 sy, 0.0 ni, 72.6 id, 0.1 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem: 8174224 total, 2335256 used, 5838968 free, 162984 buffers
KiB Swap: 8296444 total, 0 used, 8296444 free. 1219348 cached Mem

  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
 2209 st 20 0 659584 300780 39120 S 77.2 3.7 788:09.44 compiz

here it is can be caused for example by: open chrome (empty page), Version 37.0.2062.94 Ubuntu 14.10 (290621). or open some flash site. but also just have firefox open with launchpad and doing a top from time to time increases %cpu to very high values. sometimes even values greater than 100 are displayed for %CPU?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
actionparsnip
Solved:
Last query:
Last reply:
Revision history for this message
Best actionparsnip (andrew-woodhead666) said :
#1

I suggest you report a bug. Utopic is not ready and not stable. If you want an OS that works then I suggest you wipe Utopic off and reinstall with Trusty. Trusty is LTS and supported til April 2019. Utopic only has 9 months of support after release.

If you are happy to use a half-made OS with bugs and feature holes upto and even a few weeks after release, but want to report bugs to get the OS ready for release then by all means use Utopic but it is not going to be a smooth ride and is not intended for casual Ubuntu users.

You can start the bug reporting process with:

ubuntu-bug compiz

Revision history for this message
SoloTurn (soloturn) said :
#2

Thanks actionparsnip, that solved my question.