[mythtv-users] 100% CPU usage in Watch Recordings

[Isaac Richards]

On Wednesday 21 October 2009 12:30:27 am Michael T. Dean wrote:
> On 10/21/2009 12:25 AM, David Asher wrote:
> > On Oct 21, 2009, at 12:11 AM, Michael T. Dean wrote:
> >> On 10/20/2009 11:04 PM, David Asher wrote:
> >>> Is anyone else seeing this?  When I'm in Watch Recordings or Watch
> >>> Videos screen my CPU usage (via top) is 100%.
> >>>
> >>> This is a Zotac single core ION using Graphite on trunk r22497
> >>> (JYA's trunk repo).  I've tried both 185.36 drivers and 190.40
> >>> drivers (again from JYA's repo) with the same results.  It does NOT
> >>> happen with the Mythbuntu-wide theme.
> >>>
> >>> When I'm at the upper level menu items CPU usage is around 15%, but
> >>> as soon as I enter Watch Recordings or Watch Videos, the CPU usage
> >>> goes to 100% and stays there.  Not surprisingly movement is sluggish
> >>> while in these screens.  Note that this is AFTER all
> >>> previews/fanart/etc has been masked and cached locally -- its even
> >>> worse while they are brought over.
> >>>
> >>> I attached gdb to the process and the threads all look roughly the
> >>> same between the 15% and 100% usage except for Thread 1, which
> >>> appears to always be drawing something (see backtrace below).
> >>>
> >>> Any ideas?  Is this expected?
> >>
> >> Yes, this is the expected behavior.  Some themes require more
> >> resources than others.  If your system isn't powerful enough to keep
> >> up with the theme you've chosen, you should choose a different theme
> >> that uses fewer resources.
> >
> > It is expected that while sitting doing nothing in Watch Recordings to
> > utilize 100% CPU ?
> >
> > The only thing going on is the alphapulse of the "All Programs" button...
> 
> Yes*.
> 
> *Dependent on CPU.

No.  It should not be using more than a couple % CPU just sitting there idle.  
If it's using a bunch of CPU, it's likely that you're using the opengl painter 
with software rendering (ie, switch to the qt painter, that's why it exists), 
or someone broke something quite major in the UI code (file a good bug report).

Isaac