2013-01-24, 09:52
@schumi2004:
I am not quite sure :-) The only thing the DirtyRegion fliptimeout should do is a time t afterwards the screen is not flipped anymore, despite there is new stuff to Render. Idle usage has quite increased over Frodo Time, it was arround 3% in the past - you could have a look at the different threads and what they are currently doing - you can use htop or ps uH p <PID_OF_U_PROCESS> | wc -l to check - Quite curious.
As xbmc is a highly multithreaded application, one has to watch all of the threads to find what it is causing.
I am not quite sure :-) The only thing the DirtyRegion fliptimeout should do is a time t afterwards the screen is not flipped anymore, despite there is new stuff to Render. Idle usage has quite increased over Frodo Time, it was arround 3% in the past - you could have a look at the different threads and what they are currently doing - you can use htop or ps uH p <PID_OF_U_PROCESS> | wc -l to check - Quite curious.
As xbmc is a highly multithreaded application, one has to watch all of the threads to find what it is causing.