[jurialmunkey]

Usually debug log isn't that helpful for hangs/crashes but this part is a bit weird:

Code:

Infobool '!string.isempty(listitem.property(tmdbhelper.context.artwork))' still used by 3 instances

That's the condition for the context menu. Probably is nothing but can you try disabling the context menu in the addon.xml, restart Kodi and see if that helps?
Just delete out this part:
https://github.com/jurialmunkey/plugin.v...ml#L17-L40

If that's not the culprit, I'd be interested to know if it's the service monitor which can be completely disabled by taking this line out of addon.xml and restarting Kodi

Code:

<extension point="xbmc.service" library="service.py" />

If we can narrow down what part is causing the hang that will help a lot.

It's definitely the service. If I remark that out from addon.xml then Kodi quits fine (even with the context menu enabled, so that isn't it).  I added a bunch of check point logging just to see what was happening, and it seems like something is restarting the script (or the service I can't tell what) after it stops.  Here's a logfile with a single check point log line that says "the poller has stopped." I think that's an indicator that the service has shutdown (I added that log line as the last line of the run() function of the ServiceMonitor class). But you can see right after that that there are more references to the addon in the log, a few that say it's waiting on a thread, and then one saying the script didn't stop after five seconds.

https://paste.kodi.tv/azusaloqik.kodi

And just to confirm, I'm running version 4.0.8, which looks like the version that's listed in the addon.xml in the refactor-matrix branch. I'd hate to be doing all this just to find out I'm on the wrong version.

Yep v4.0.8 from refactor-matrix branch is the correct one (well it's now 4.0.10 but only because I just pushed a few changes).

Good to know it is the service. I suspected that was the cause but good to have confirmation.

The "script successfully run" messages are normal and indicate (very counter-intuitively) that the script got to the end of the code, not that it is starting up. You can see there were two instances (3) and (15) of the service. The (15) one completed properly because it got "onExecutionDone" but the (3) one didn't clean up whatever thread it had going and Kodi tried to kill it. That'd be where the hang is.

Can you test with v4.0.10 that I just pushed to the refactor-matrix branch? I added in some additional exit conditions. I tested on a fresh portable install of Matrix Alpha 2 using Arctic Horizon (I only installed AH and it's dependencies) and it has exited cleanly every time for me so far with these changes.