You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When Mopidy-AlarmClock is loaded (granted, with my changes, but I think this is unrelated to them), service mopidy restart seems to take a loooong time. There are no logs pointing the finger at anything, but my suspicion is that the timer thread (or threads, if they're constantly being created) are not getting the signal to shut down.
I looked around and Mopidy-GMusic also has a repeating timer, and its Pykka-aware backend seems to get an on_stop message that tells it to kill its timer. But I don't know how we can do the same thing without significantly changing.
The text was updated successfully, but these errors were encountered:
rgov
changed the title
Mopidy takes a long time to restart when using Mopidy-AlarmClock
Mopidy takes a long time to shut down when using Mopidy-AlarmClock
Mar 6, 2017
When Mopidy-AlarmClock is loaded (granted, with my changes, but I think this is unrelated to them),
service mopidy restart
seems to take a loooong time. There are no logs pointing the finger at anything, but my suspicion is that the timer thread (or threads, if they're constantly being created) are not getting the signal to shut down.I looked around and Mopidy-GMusic also has a repeating timer, and its Pykka-aware backend seems to get an
on_stop
message that tells it to kill its timer. But I don't know how we can do the same thing without significantly changing.The text was updated successfully, but these errors were encountered: