2010-11-18, 11:30
I am a long time XBMC user and I'm aware of the high CPU quirks XBMC has been having over the years.
I've always used a relatively simple dedicated HTPC hooked on a CRT (Celeron 1300/Geforce 5200) running 9.11 and a 4:3 skin and really NOT using fanart but just the file mode for viewing content.
Recently I've bought a LG 55LX9500 and hooked up my Scaleo-E (P4 3ghz, Geforce 210, Dharma beta 4, vanilla gui settings) finally to really enjoy my extensive Media content from a 4tb network server on the large screen.
It scared the hell out of me........
While browsing through my video library my fans are going ape ****!!! It's like a plane taking off.
When bringing up the debug overlay, it shows CPU's usages up to a staggering 155% (CPU-XBMC), 100% core 1, 55% core 2 .
What can possibly justify a CPU usage that kind? Of all the programs I've ever used over the years, I've never had ANY program reaching those numbers, apart from programs hanging the system.
So what's causing this?
Furthermore, what can be done until this is resolved?
Normally I would send a debug, but I'd really like some pointers where to look in the debug file first.
I've always used a relatively simple dedicated HTPC hooked on a CRT (Celeron 1300/Geforce 5200) running 9.11 and a 4:3 skin and really NOT using fanart but just the file mode for viewing content.
Recently I've bought a LG 55LX9500 and hooked up my Scaleo-E (P4 3ghz, Geforce 210, Dharma beta 4, vanilla gui settings) finally to really enjoy my extensive Media content from a 4tb network server on the large screen.
It scared the hell out of me........
While browsing through my video library my fans are going ape ****!!! It's like a plane taking off.
When bringing up the debug overlay, it shows CPU's usages up to a staggering 155% (CPU-XBMC), 100% core 1, 55% core 2 .
What can possibly justify a CPU usage that kind? Of all the programs I've ever used over the years, I've never had ANY program reaching those numbers, apart from programs hanging the system.
So what's causing this?
- the relatively old nvidia driver shipped with dharma
- network activity (reading fanart from a share)
- inconsistencies in the underlying OS
- or.........God forbid, some bad code
Furthermore, what can be done until this is resolved?
- update the nvidia driver
- use dds fanart
- wait for the final dharma
- some other solution
Normally I would send a debug, but I'd really like some pointers where to look in the debug file first.