2013-02-08, 18:05
Hi,
I don't remember if I already reported the issue but I just tried the addon again on frodo and still had the same issue.
I saw, some other user reported the issue too.
The issue I have is, that I get a really high cpu usage when I had enabled the addon. Process Explorer shows that its more a kernel cpu usage instead of a xbmc process usage
My setup.
I have all stuff on another computer (both windows 7). I use CIFS and had mapped all the volumes on the client where xbmc is running.
I never shutdown my client. I only reboot it when necessary. I only use standby to ram. I use Eventghost to exit xbmc before enter standby and start it again after waking up the client.
I think its only after waking up the client and start xbmc that the addon or the system went crazy.
Last time i switched back to the other addon xbmc auto update library but that gave me some problems on frodo after the migration, so I retried this addon.
I don't know if this is fixable but I would like to try to give you all the info I can get.
Do you or anyone watching this thread had seen this issue too?
I don't saw any entries regarding this issue in the debug log of xbmc.
I don't remember if I already reported the issue but I just tried the addon again on frodo and still had the same issue.
I saw, some other user reported the issue too.
The issue I have is, that I get a really high cpu usage when I had enabled the addon. Process Explorer shows that its more a kernel cpu usage instead of a xbmc process usage
My setup.
I have all stuff on another computer (both windows 7). I use CIFS and had mapped all the volumes on the client where xbmc is running.
I never shutdown my client. I only reboot it when necessary. I only use standby to ram. I use Eventghost to exit xbmc before enter standby and start it again after waking up the client.
I think its only after waking up the client and start xbmc that the addon or the system went crazy.
Last time i switched back to the other addon xbmc auto update library but that gave me some problems on frodo after the migration, so I retried this addon.
I don't know if this is fixable but I would like to try to give you all the info I can get.
Do you or anyone watching this thread had seen this issue too?
I don't saw any entries regarding this issue in the debug log of xbmc.