Posts: 85
Joined: Jan 2011
Reputation:
0
2013-10-06, 14:57
The system boots fine and works great until you scroll down a list (quickly) then the CPU usage runs up to 100% on "both CPUs" and stays there, which in turn makes for choppy audio.
System Config:
Lastest (as of 10/6) 12.2 XBMCbuntu
dual core AMD 3 GHz Processor
Radeon 7600
4 GB RAM
2 TB HD
4 TB HD
I've added the dirty region stuff to the advancedsettings.xml, that didn't seem to help, I also updated to the latest video drivers, I turned on the debug log but didn't see anything that looked like it would help.
* One other weird thing:
when I log in to Ubuntu the desktop the desktop doesn't refresh correctly, I get "ghost" images of all the windows on the screen
Thanks everyone
Posts: 5
Joined: Jul 2014
Reputation:
0
2014-07-19, 11:21
(This post was last modified: 2014-07-19, 11:23 by maxadamo.)
This is a bug in in the interface (I don't know if it depends on the theme, but it happens to me with Confluence).
If you leave the "home" screen, and go to any of the setting pages, you won't see the high cpu usage any longer.
p.s.: the dirthyregion setting if it's not a scam, it's a waste of time.
Posts: 31,445
Joined: Jan 2011
(2014-07-19, 11:21)maxadamo Wrote: This is a bug in in the interface (I don't know if it depends on the theme, but it happens to me with Confluence).
If you leave the "home" screen, and go to any of the setting pages, you won't see the high cpu usage any longer.
p.s.: the dirthyregion setting if it's not a scam, it's a waste of time.
You think you've been swindled by the dirtyregions setting? wat?
Just because it did not lower CPU usage for you doesn't mean it isn't an actual feature of XBMC that does work. There's countless reasons why there might be an issue in this situation. I understand that you're frustrated, but please don't go spouting nonsense on the forum.
If you'd like to get to the bottom of your issue then update XBMC to v13 and try again. If there is still an issue then please provide a
debug log (wiki), which will tell us more information.
Posts: 5
Joined: Jul 2014
Reputation:
0
2014-07-20, 16:38
(This post was last modified: 2014-07-20, 17:22 by maxadamo.)
If you want to know more I have found a workaround, which is suitable for me.
As I use the autologin feature of the Login Display Manager in Linux (in order to have all the services available, web interace and upnp and so on) I have just changed the "starting screen" section to "settings", instead of "home".
In this case the CPU usage goes to 3%
p.s.: I don't know the exact name of this option as I am using the Italian localization: however, after login I get the "setting screen" and not the "home" screen.
I don't use any fancy screen saver: dim screensaver by default.
Even if I disable "dim" screensaver nothing changes.
Posts: 31,445
Joined: Jan 2011
2014-07-21, 09:25
(This post was last modified: 2014-07-21, 09:26 by Ned Scott.)
Dirty regions most likely didn't have any effect because it's been enabled by default since v12. In other words, adding or removing it from advancedsettings.xml didn't change anything, because the most basic functions were always on no matter what.
The debug log isn't going to just flat out say "this is the problem". Rather, we need the logs to gather information, like what GPU hardware you are using, if XBMC was doing any kind of scanning or even just checking for updates (even though those are supposed to be normal functions), what messages, if any, is Confluence giving about the situation (or even the lack of information might indicate something), etc. Unless you actually understand XBMC's programming then you can't really conclude that the log doesn't contain any useful information.
High CPU usage could be a symptom of any number of issues, and we can't even be sure that you are having the same issue that the original poster had.
Posts: 17,859
Joined: Jul 2011
Reputation:
371
there were fixes done in the dirtyregion code that reduced CPU on home screen
Posts: 6,810
Joined: Jul 2010
Reputation:
198
If you have the RSS feed on the home screen enabled dirty regions won't show any effect because the content on screen is constantly changing. Rendering the GUI at 60Hz puts a lot of load on the ION GPU. The closer the GPU gets to its limits the more CPU load you can observe.