Posts: 13
Joined: Dec 2009
Reputation:
0
Mirt
Junior Member
Posts: 13
I tried the settings stated by jmarshall. Sadly, they didn't fix the problem for me. I also tried the <bginfoloadermaxthreads>-setting but that didn't make a difference either.
Posts: 26,215
Joined: Oct 2003
Reputation:
187
Riddle me this:
1. How long do the background images on home take to load?
2. Do a full debug log with you:
a) Loading XBMC.
b) Going to Movies.
c) Staying on the first movie until it's fanart is shown.
d) Moving to the next movie as soon as the first fanart is shown.
e) Stay on that movie until it's fanart is shown.
f) Repeat from d) 10 times.
Then post the log.
Posts: 13
Joined: Dec 2009
Reputation:
0
Mirt
Junior Member
Posts: 13
I did a build from svn yesterday and now I have another problem. After restarting XBMC, debugging is disabled although the checkbox in System->Debugging is ticked. So I can only post incomplete debug logs, i.e. I have to toggle debugging after launching to enable it again. I'll post a new log soon as this has been sorted out.
Incidentally, I did what you said in my debug log which I posted a while ago in this thread.
After looking at all the debug logs posted by people here I noticed that they have all one thing in common: System CPU is a single core CPU.
I have no idea about how xbmc is implemented, but maybe there is somewhere a bug with threading. Maybe the fanart-loader-thread doesn't get the priority/attention it should get or there is a problem with temporary lockup due to semaphores/mutexes which gets noticeable on systems with only 1 core. Just a hunch.
Posts: 26,215
Joined: Oct 2003
Reputation:
187
All: Add this:
<sleepbeforeflip>0.9</sleepbeforeflip>
to advancedsettings.xml. That is the ONLY change that could have affected things from Alpha2 to Beta1.
Cheers,
Jonathan
Posts: 26,215
Joined: Oct 2003
Reputation:
187
Magic. I consider this closed then.
Posts: 75
Joined: Nov 2009
Reputation:
0
could I ask for a little detail on what this changes, and why it was changed in the beta? (and will the need for this advancedsetting.xml change remain in future versions?)
Posts: 26,215
Joined: Oct 2003
Reputation:
187
It was forced on in alpha2 (and possibly alpha1, I can't recall offhand).
It's for crappy graphics drivers that busy wait on vsync. i.e. the app thread is sitting there waiting for the GPU to finish and doesn't yield for any other threads (in this case background loading) to finish. Thus the background loaders which have lower priority take forever to complete.
ATI seems the worse, but I've heard other reports from Intel and some nVidia boards. Only really seems an issue on XP - Aero seems to take care of it on Vista and higher.
Cheers,
Jonathan
Posts: 75
Joined: Nov 2009
Reputation:
0
Ok, thanks for the explanation.
There must be some side effect that causes it to just reduce CPU overhead since my system is windows 7 with the recent nvidia video beta driver and an older (but not crappy (or is it by now?)) 6600GT
Posts: 1,165
Joined: Jan 2009
Reputation:
2
CrashX
Posting Freak
Posts: 1,165
Wow it does fix the high cpu usage in beta build in fullscreen idle mode. I had 55% before and 20% after fix. Using XP ATI X1400PRO.
The normal XBMC log IS NOT a debug log, to enable debug logging you must toggle it on under XBMC Settings - System or in advancedsettings.xml. Use
XBMC Debug Log Addon to retrieve it.