Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account loaded about 83 times every 2-3 seconds #477

viulian opened this issue May 17, 2018 · 2 comments


Copy link

@viulian viulian commented May 17, 2018


I'm running the latest 2.0.25 plugin on LibreELEC / Raspberry Pi 3b+ and I'm trying to debug high load even when things are idling.

Attaching to the thread that occupies the most CPU, strace reports about 83 lines (about 2-3 seconds) that look like:

open("/storage/.kodi/addons/", O_RDONLY|O_LARGEFILE) = 68
open("/storage/.kodi/userdata/addon_data/", O_RDONLY|O_LARGEFILE) = 68
open("/storage/.kodi/addons/", O_RDONLY|O_LARGEFILE) = 68
open("/storage/.kodi/userdata/addon_data/", O_RDONLY|O_LARGEFILE) = 68

After a reboot, it looks like the Music library is being refreshed, few popups that sync had to skip some items appear. After dismissing them, one thread starts reading the plexkodiconnect settings.xml very often, driving the CPU load high. There are no kodi.logs as this is happening ...

I understand from the popup that Kodi may be unstable, BUT why is kodi interested only in the settings.xml of plexkodiconnect and not on the other plugins :) ?

PS: CPU load (longterm) is about 0.80, and CPU usage hovers around 50% ...

Thank you,

Copy link

@croneter croneter commented May 17, 2018

Please share your entire debug log as explained in the wiki here on Github - this will allow me to understand the context

Copy link

@viulian viulian commented May 17, 2018

The log file is huge, 12Mb and increasing ... so I started digging.

For now, there is a problem with this file as it is constantly written to:


The value updated very often is:

<setting id="caching_artwork_count" value="XXXXX" />

Which means onSettingsChanged(self) will constantly get called by Kodi, loading the system even more.

I guess I have to tolerate a very high load until everything finishes - thank you for the hint with the debug, there it was obvious the line:

19:25:46.050 T:1759507360 DEBUG: PLEX.kodimonitor: PKC settings change detected

It feels like a bug, but I don't see an immediate solution to it - except moving this status counter in a separate status file - instead of a setting (which would imply the user could change it, but he can't, is just a status).

@croneter croneter closed this in 84c2aa7 May 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants