OK, so even with debugging set to level 2 I’m still struggling to identify the offending process or trigger.
In order to eliminate System Updates or Backups from the equation, I scheduled those for 8:30am… At that time there were no memory spikes or solid lights.
On the up-shot, I have without question discovered that the issue will occur at exactly 24 hours uptime. I also know that it can go for as little as 10 minutes or even 1 hour and 10 minutes like it did tonight. Every time it will culminate in a Sad Face and Kodi will restart. I don’t know what that means… I’ve been trying to work out what happens at 24 hours uptime to no avail.
I’ve uploaded tonights logs here: https://paste.osmc.tv/iwakakivag
Tonight I remoted in and watched the performance via htop. Initially there was a slight increase in CPU but by 22:13 I had 84.8% memory used by kodi.bin… and CPU was negligible… this held the entire time… and the activity light was solid throughout. The kodi.bin process had 50/51 threads the entire time. I do have some screenshots of the htop output if anyone is interested.
Now, usually I only see a gap in my logs but tonight I have the following sequence repeating during this time…
22:16:54.007 T:1087365888 DEBUG: Thread JobWorker 1087365888 terminating (autodelete)
22:17:04.251 T:1925831168 INFO: CheckIdle - Closing session to http://www.msftncsi.com (easy=0x49437090, multi=(nil))
22:17:46.166 T:1087365888 DEBUG: Thread JobWorker start, auto delete: true
22:17:50.957 T:1087365888 INFO: easy_aquire - Created session to http://www.msftncsi.com
22:18:01.653 T:1087365888 ERROR: CCurlFile::Exists - Failed: Timeout was reached(28) for http://www.msftncsi.com/ncsi.txt
22:18:09.989 T:1087365888 INFO: easy_aquire - Created session to http://www.w3.org
22:18:17.892 T:1087365888 ERROR: CCurlFile::Exists - Failed: Timeout was reached(28) for http://www.w3.org/
Again, I don’t know what I’m looking at here… Apparently those URLs have something to do with testing network connectivity. I can’t tell if this is relevant to the issue or not.
I looked again through the forum… I found a reference to “100% cpu and frozen picture” which mentioned turning off UPnP:
I guess I’ll try that next. I don’t know what else to do. This is really starting to get me down. I don’t understand why it’s so difficult to find out what Kodi is doing (and why) at a given time.
Anyone?