[BobCratchett]

Fair warning: Long, boring and technical post ahead.

Here's a debug log : https://dl.dropboxusercontent.com/u/110057345/kodi.log

I will take a look on the link given by Mr V.
Meanwhile, if you find something unusual in this...

Thanks in advance !

Looking at your log, there is an error related to python.

Code:

00:09:22 T:652   ERROR: C:\Users\Dam\AppData\Roaming\Kodi\addons\script.module.requests\lib\requests\packages\urllib3\util\ssl_.py:315: SNIMissingWarning: An HTTPS request has been made, but the SNI (Subject Name Indication) extension to TLS is not available on this platform. This may cause the server to present an incorrect TLS certificate, which can cause validation failures. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#snimissingwarning.
                                              SNIMissingWarning
00:09:22 T:652   ERROR: C:\Users\Dam\AppData\Roaming\Kodi\addons\script.module.requests\lib\requests\packages\urllib3\util\ssl_.py:120: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
                                              InsecurePlatformWarning

I am not sure what to make of it or what plugin is causing the issue. I am open to suggestions from anyone that has an idea what the issue is. But my gut feeling is that there is an issue with one of your plugins.

That particular error shouldn't make any difference with getting information out of the local library - the requests module is used to retrieve information from a server and, whilst Kodi has an inbuilt server, widget providers normally use the python api to get the info they need. (And even then, the error will only affect SSL connections). I suspect that can be safely ignored for this particular issue.

There's also none of the traditional signs that a script has 'stalled' - most notably, you'd see Kodi killing the script on exit, but all scripts are exiting in a timely manner.

What is interesting is the Library Data Provider logging. That particular widget provider (unless things have changed dramatically since I contributed to it) is two different scripts working in unison - a service and a plugin. The service retrieves and keeps up to date the library data that the widgets will be built from, the plugin actually builds the widgets.

Now, the plugin side of the addon appears to be working absolutely perfectly. As much as I hate log snippets, here's a snippet showing that:-

Code:

00:09:24 T:13432   DEBUG: XFILE::CPluginDirectory::StartScript - calling plugin Library Data Provider('plugin://service.library.data.provider/','5','?type=recentepisodes&reload=20160308230923')
00:09:24 T:13432   DEBUG: XFILE::CPluginDirectory::WaitOnScriptResult - waiting on the Library Data Provider (id=21) plugin...
00:09:24 T:10292   DEBUG: CPythonInvoker(21, C:\Users\Dam\AppData\Roaming\Kodi\addons\service.library.data.provider\default.py): start processing
00:09:24 T:10292   DEBUG: CPythonInvoker(21, C:\Users\Dam\AppData\Roaming\Kodi\addons\service.library.data.provider\default.py): the source file to load is "C:\Users\Dam\AppData\Roaming\Kodi\addons\service.library.data.provider\default.py"
00:09:24 T:10292   DEBUG: CPythonInvoker(21, C:\Users\Dam\AppData\Roaming\Kodi\addons\service.library.data.provider\default.py): instantiating addon using automatically obtained id of "service.library.data.provider" dependent on version 2.1.0 of the xbmc.python api
00:09:24 T:10292   DEBUG: Library Data Provider: script version 0.1.5 started
00:09:25 T:10292   DEBUG: Library Data Provider: script version 0.1.5 stopped
00:09:25 T:10292    INFO: CPythonInvoker(21, C:\Users\Dam\AppData\Roaming\Kodi\addons\service.library.data.provider\default.py): script successfully run

So that means that the problem is in the data that the service element of the script is gathering, and indeed it does seem to manage it all very quickly:-

Code:

00:09:15 T:3008   DEBUG: Library Data Provider: service version 0.1.5 started
00:09:16 T:3008   DEBUG: Library Data Provider: Total time needed for all queries: 0:00:00.390000

Less than half-a-second to get all the needed data is very quick. Of course you may just have a very quick system, but on my own system this process takes over half a minute.

This is where things get less clear, though. Looking at what happens between the service being started and all queries being completed, I can see the queries and I can see media being returned - for example:-

Code:

00:09:15 T:3008   DEBUG: CVideoDatabase::RunQuery took 1 ms for 31 items query: select * from movie_view  WHERE (movie_view.idFile  IN (SELECT DISTINCT idFile FROM bookmark WHERE type = 1))

Now, there isn't a lot of media being returned, but it's definitely there and that would suggest the service is doing its job correctly. Add to that the fact that reloading the skin really shouldn't affect Library Data Provider, where the separation of service and plugin exists, and I'm utterly confused