2011-01-16, 01:30
I just installed xbmclive 10.0 Dharma on my pc. I installed it to the hard drive, and it boots and looks and seems to work great. I tested playing some files, and all was well. So I started to add sources to populate the library.
I started updating my library, and xbmc was happily scanning in new tv shows. The debug dialog at the top of the screen showed low CPU usage, and 60 fps. At some point, all of a sudden the fps drops to less than 1. Key presses on keyboard and remote then start taking 5-10 seconds to register. It sits like that for a long time, and seems to be almost frozen - I can't open a different console to even check the log file.
And then, after letting it sit for a while (at least 5-10 minutes), the screen goes black, and it appears to re-launch xbmc (goes back to the main menu and everything). This is seemingly confirmed as a new xbmc.log file is started. The dialog at the top indicates it's still scanning in files, although it seems to stop after the show it's on (doesn't progress to the next show). And key presses start registering like normal.
Is this normal? Should xbmc become virtually unresponsive while scanning in files? If it matters, the files are located on a samba share on my WHS, and it was a large directory. I'm not exactly hard up on CPU or RAM, either (~2.2ghz dual core AMD, 2 gigs RAM).
Here is the current log: http://pastebin.ubuntu.com/554526/
And here is the old log: http://pastebin.ubuntu.com/554527/
The strangest part of this is that the scan goes fine, and the system is very responsive, and then all of a sudden it's not anymore. Very strange.
Can anybody help?
Thanks!
I started updating my library, and xbmc was happily scanning in new tv shows. The debug dialog at the top of the screen showed low CPU usage, and 60 fps. At some point, all of a sudden the fps drops to less than 1. Key presses on keyboard and remote then start taking 5-10 seconds to register. It sits like that for a long time, and seems to be almost frozen - I can't open a different console to even check the log file.
And then, after letting it sit for a while (at least 5-10 minutes), the screen goes black, and it appears to re-launch xbmc (goes back to the main menu and everything). This is seemingly confirmed as a new xbmc.log file is started. The dialog at the top indicates it's still scanning in files, although it seems to stop after the show it's on (doesn't progress to the next show). And key presses start registering like normal.
Is this normal? Should xbmc become virtually unresponsive while scanning in files? If it matters, the files are located on a samba share on my WHS, and it was a large directory. I'm not exactly hard up on CPU or RAM, either (~2.2ghz dual core AMD, 2 gigs RAM).
Here is the current log: http://pastebin.ubuntu.com/554526/
And here is the old log: http://pastebin.ubuntu.com/554527/
The strangest part of this is that the scan goes fine, and the system is very responsive, and then all of a sudden it's not anymore. Very strange.
Can anybody help?
Thanks!
