[Tobby]

That log isn't very helpful, as mentioned, but I can tell you now that there's not much I can do about it. Part of how AutoWidget works is that it has to do a "fake" library update in order for widgets to know that they have new content. Without this update, widgets would only change whenever you rebooted Kodi.

AutoWidget runs its service every 15 minutes, but by default, only refreshes widgets every 2 hours, if you modify active widgets, or change pages in a paged widget. I worked very hard to reduce the number of updates necessary for proper functioning as much as  I could, but there still have to be some of them.

I would recommend doing exactly what you've done: disable AutoWidget until your full library is done scraping.

Well that explains it. That's fine, really. It's not like I rescrape my library every day, so it's not much of a hassle. I was really scratching my head before I found the reason behind the issue though.

However I assume you're doing a refresh when Kodi starts and that interrupts the library scan on startup before it's finished. Would it be possible to skip the refresh on startup if I have library scan set to run at startup anyway? Either with a toggle in the add-on settings, by reading the toggle to scan on startup or not running the refresh while already scraping. Not a dev, so I don't really know which of the options is within the scope of possibility. I would be grateful of you considered it though.

Also I can try getting a better log file from startup if you, or @scott967 are interested.

The drawback to not having them refresh on boot would be that if a widget is scheduled to refresh at boot, it won't refresh until the service runs again, a minimum of 15 minutes later. I feel that this would detract from the dynamism of the add-on... However, unless your entire library is being scraped at every boot (probably unnecessary), there shouldn't be too big of a problem there.

Wouldn't they refresh at startup anyway since my library is scanned?

No obviously I don't rescrape my entire library at every start up, but still the library scan gets interrupted before it has had time to look through the first disk, which kind of defeats the purpose of having the library scan on startup toggle enabled at all.