[windsorguy1979]

If you don't mind me asking... what makes you believe this has anything to do with your problem? other then you see a print of it on your log? Just wondering...

Anyway, refreshLock doesn't call new threads, then abandon them. It's only called once, and doesn't run more then one thread.

Debugging by guessing . refreshLocks is the only thing active in my logs when this issue starts and returning False right away was the only change I made and seems to have solved my issue. Python isn't my bread and butter but I was looking at "self.refreshLocksTimer = threading.Timer(4.0, self.refreshLocks)" and thinking that was spinning up a new thread but not seeing anything to kill the old thread. I just re-read the timer API that while it is true that it is starting a new thread, the old thread stops when refreshLocks ends. Looking at this now, I'm not sure why this change seems to have corrected my problem. What is this method for anyhow? Not looking for a fix in the codebase, this might be a one-off that I run on my system that works for me for some reason.

It's part of channel sharing and file locking... it runs once, every 4 minutes as designed. If you could send me a log when you experience your problem I could provide further input.

That may be why I'm seeing so many of these in my log file and why it may be bogging down my FireTVs. Looking at the Timer API, the interval '4.0' is 4 seconds, not 4 minutes, correct? Which means refreshLocks is running every 4 seconds. I'm looking at this for reference: https://docs.python.org/2/library/thread...er-objects