Closed
Description
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:127.0.0.1]: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.
Metadata
Metadata
Assignees
Labels
No labels