A coherence trouble ticket [1] indicates that there is a 100% CPU bug in pygobject and that the user should upgrade to 2.21.0. I have experienced this CPU issue and after copying the 2.20.0 ebuild to my local overlay and updating the version to 2.21.0 the 100% CPU issue is resolved. [1] - http://coherence.beebits.net/ticket/284 Reproducible: Always Steps to Reproduce: 1. emerge coherence with pygobject 2.20.0 2. run top 3. observe coherence using 100% CPU Actual Results: Coherence uses 100% CPU Expected Results: Coherence does not use 100% CPU constantly.
2.21 versions are development, we should try to find the exact commit fixing this instead :-/
This could be the commit: http://git.gnome.org/browse/pygobject/commit/?id=a9c168c58cc6a449b51653417bf3f58bdd41457c Please try to apply the following patch to 2.20: http://git.gnome.org/browse/pygobject/patch/?id=a9c168c58cc6a449b51653417bf3f58bdd41457c Good luck!
(In reply to comment #2) > Please try to apply the following patch to 2.20: > http://git.gnome.org/browse/pygobject/patch/?id=a9c168c58cc6a449b51653417bf3f58bdd41457c Just a note. From here: https://bugzilla.gnome.org/show_bug.cgi?id=481569 >When this patch for pygobject is backported to version 2.20, moovida becomes >unresponsive (input events are very slow to be processed).
Created attachment 236147 [details] pygobject ebuild ..for those who're looking for a bugfix: here is "dirty" ebuild for pygobject from Git. Dependencies can be found in gnome overlay, but it looks like pygobject snapshot from there doesn't contain the fix yet.
*bump*. gnome folk, status?
We will add the upstream patch to 2.20.
What patch should be included finally?
pygobject-2.26 is in the tree and should fix this
