Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mopidy takes a long time to shut down when using Mopidy-AlarmClock #9

Open
rgov opened this issue Mar 6, 2017 · 0 comments
Open

Mopidy takes a long time to shut down when using Mopidy-AlarmClock #9

rgov opened this issue Mar 6, 2017 · 0 comments

Comments

@rgov
Copy link

rgov commented 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.

@rgov 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant