mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #183] Crash in the middle of playback (ChannelError) #125
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#125
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @l3d00m on GitHub (Mar 6, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/183
Edited the issue as it just happened again and I was able to offer a more detailed description
This crash happened in the middle of playback without any kind of input from my side, playback just stopped. The interesting thing here is that the
raspotifyservice / librespot did not terminate immediately, but rather as soon as I clicked play in the client again. This finally crashed librespot with aSendError(Notice: This log is not truncated between the two errors)Debug info:
librespot (raspotify) 593dfa0 (2018-02-27). Built on 2018-03-01. Build ID: tKkd5pOH@sashahilton00 commented on GitHub (Mar 10, 2018):
I'm not actually sure what is causing this, as the backtrace doesn't say much. Anyone care to weigh in with any thoughts? From the behaviour you described, I'm inclined to think #134 is related, as I've seen that hit play to cause crash behaviour with that bug.
@ComlOnline commented on GitHub (Mar 10, 2018):
I'm thinking its something like #172 where there error doesn't cause a panic, until something else fails. I cant see anywhere to point a finger though.
EDIT: Well the first error does cause a panic so... 😕
@sylbarth commented on GitHub (May 22, 2018):
Hi,
Having the same problem after a few songs.
and only a
systemctl restart raspotifycorrect the problem.But as far as I remember, it used to work perfectly in the past, and do not remember doing any update/upgrade. So, maybe a change on the Spotify side?
@l3d00m commented on GitHub (May 22, 2018):
It usually crashes if you try to play the next song, this avoids having to log in via ssh @sylbarth
See also #226
@ComlOnline commented on GitHub (Jun 4, 2018):
@l3d00m your comment from #215 seems to indicate that this is resolved (in that it no longer happens, not that we know what caused it.) would you say that is the case for this as well?
@l3d00m commented on GitHub (Jun 4, 2018):
I could just reopen if it should occur again, librespot was pretty stable in the last days
@ComlOnline commented on GitHub (Jun 4, 2018):
That's good to hear, in that case that may be easiest.
@l3d00m commented on GitHub (Jun 5, 2018):
It did happen again yesterday for me, that was quick. Same error as above. This seems to be the most frequent crash for me (I'm using librespot nearly 12 hours a day)
@1337sup3rh4x0r commented on GitHub (Dec 7, 2018):
Hi there,
I am seeing the same bahaviour for a specific track ("spotify:track:6W2i0WRMkwj5IY4g2PAc3M"). Every time I try to play it, librespot crashes reproducibly with the same SendError I see in @l3d00m's report:
@torbatschow commented on GitHub (Dec 13, 2018):
Same here, with
INFO:librespot: librespot d2cadec (2018-11-19). Built on 2018-12-13. Build ID: cu4INf0WFor some reason it only happens with certain tracks. "Skating In Central Park" works just fine, "Blue Monk" from the same album does not:
Full error / panicking below:
@zkiiito commented on GitHub (Dec 13, 2018):
happens about hourly on my rpi :(
@1337sup3rh4x0r commented on GitHub (Dec 14, 2018):
I think @kingosticks pointed towards what is going wrong here in #280.
The way I understand it, is that spotify is slowly starting to serve more and more songs via some content delivery network and no longer directly via their initial servers. Librespot is not able to handle this different song source (yet).
@roderickvd commented on GitHub (May 25, 2021):
Was fixed upstream on Spotify's end.