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
EOT changes makes "next" deadlock Mopidy #316
Comments
I think this is caused by I'm experiencing this playing from Spotify. I haven't tried with local music. |
I can still reproduce this on develop, now using another machine. Using our beloved debug thread, this is quite debuggable. The MPD session blocks waiting for core:
Core waits for the backend:
The Spotify backend waits for audio:
Audio is in the middle of calling it's about to finish callback, and are thus waiting on core, biting it's own tail. Deadlock is a fact.
|
The reason the about-to-finish callback works for EOT is because that is caused by audio not having more data to play, and not a blocking call all the way down from a frontend through core. I guess the solution here is to break the block chain. Another solution would maybe be to go to consider reimplementing |
I have been experiencing the same problem as jodal. Is there a fix on the way for this? It unfortunately makes Mopidy unusable. Alternatively, is there a way around the problem that anyone is aware of? |
The solution until we're done with a cleanup of |
The EOT changes have now been reverted out of the develop branch. A new pull request #346 with the EOT changes has been opened. This issue is still relevant for that pull request. |
I'm closing this issue as the code causing it was reverted 7 months ago, and we've now closed the pull request which would reintroduce the changes in a fixed form. |
To reproduce:
Result: Audio stops, everything becomes unresponsive.
The text was updated successfully, but these errors were encountered: