It's neither a pigment problem (text.py, sphere.py from the examples run fine at 2% cpu usage), nor is it the media scanner scanning for files. Elisa constantly uses up 100% cpu no matter if idling, watching movies, looking at pictures or listening to music. It's 98% for /usr/bin/elisa and 0.5% for gst_metadata_runner.py

cpu at 100 % with elisa 5.37 on ubuntu jaunty => critical
when using new web plugins (games, movies or grooveshark...)

Note:
reading movie .avi or dvd = CPU's behaviour OK

other problems:
*bad integration of new gnome notifications (jaunty)
*triptic "minimize/resize/close" is sometimes present on primary menu (and more times not)
*Backspace do not close elisa but resize it and the top of the window is hide by the taskbar...

comments:
*Good idea the menu "slideshow" on the right top... but why not a such a selection in the primary menu to configure the "slideshow view" for all choices (videos, music...)
*Bad integration of weather plugin - unusefull there where it is (and how configure it ?)
*There is no link to the to reading track when moving inside elisa menu (music video ..)
*Why not a button "Exit"?

By the way.... congratulations for this mediacenter... I understand why ubuntu team support it!
thks.

First of all, I've checked if it's a Pigment bug by running python-pigment examples. They run fine so it's not. Second thing i have done was checking what is Moovida actually doing with strace and I found out that this (running again and again):

Note couple things:
- it looks like it's a poll loop running all the time consuming 100% CPU
- poll is returning 1 FD ready (fd=8)
- this fd is NEVER READ (?!)
- after this, fd=11 is read and there is next poll immediately (check out gettimeofday values)
- next poll returns immediately with fd=8 since it wasn't read before.. this continues forever and uses all the CPU

Thanks for your very thorough investigations Krzysztof.
I cannot tell where exactly the problem is, but I know that some time ago people at Fluendo suggested that using the GTK2 reactor is useless and that we could save memory usage by getting rid of it. Maybe time to evaluate this solution? Could potentially fix the problem, or at least simplify it by removing one of its components.

Conclusion is that this is pygtk bug. They have a patch in their bug trucking system but since it is not included in the mainstream (it has one corner case). Twisted does not want to create any workaround so it seams there are 2 possibilities:
- get rid of using gtk2reactor, as Olivier said
- fix mainstream pygtk

Note that this issue will be more and more common for all users as they switch to python 2.6.

Hmm some precisions to add. pygtk & pygobject are both broken but in the case of Moovida it is pygobject that needs fixing. The glib2reactor uses a pygobject main loop, AFAIK. And Moovida uses pygtk only for the splash screen, which is unrelated with this bug.