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

Playback sometimes stops at end of track using Despotify #10

jodal opened this Issue Jun 24, 2010 · 2 comments


1 participant

jodal commented Jun 24, 2010

Using Mopidy 4e29754 and Despotify/spytify r508. At the end of a track, after having listened to a couple of tracks, Mopidy's core process (pid 28016 below) no longer responds upon requests from the MPD server process (pid 28015 below).

DEBUG    2010-06-24 20:56:03,647 [28016:Dummy-1] mopidy.backends.despotify
  Despotify signalled end of playlist
DEBUG    2010-06-24 20:56:04,049 [28015:MainThread] mopidy.mpd.server
  Input from [::ffff:]:48995: status
... no response ...

Core process is waiting on something:

jodal@kih:~$ strace -p 28016
Process 28016 attached - interrupt to quit
futex(0x290a0a0, FUTEX_WAIT_PRIVATE, 2, NULL

The MPD server process is still living and accepting connections, but won't answer any requests as it is reusing the locked up core process.


This comment has been minimized.


jodal commented Aug 2, 2010

This also sometimes happen when playing a track and selecting another track to play.

I wonder if we should stop the previously playing track before playing the next.


This comment has been minimized.


jodal commented Aug 23, 2010

DespotifyBackend is removed in 0.1.0 which now is released.

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment