12-17-2018, 08:02 PM
There are 59 open issues in the librespot github repo. A number of them have the word "crash" in their title. The reported symptoms vary, since usage varies, as do the guesses of the causes. Frequently a momentary interruption of Internet service is hypothesized. I found this comment from a maintainer in response to a recent issue
According to the current build_recipe_v2.7.txt, librespot is being built from the sources at commit a4e0f58 which dates back to August. While it isn't clear from the github log just what issues the subsequent commits are likely to resolve, you could try building from the current sources on the master branch and see if you get a more-stable result.
I'm able to listen to Spotify for hours here---Spotify app on a iPad, moOde r4.4 on an RPi3B+ connected via WiFi, decent ISP connectivity via Verizon FiOS. Maybe I've just been lucky but I haven't run into the issue reported here.
Regards,
Kent
Quote:My gut feeling is that this is a combination of Connect being buggy, and also is not handling reconnections. I suspect if/when we get around to implementing reconnection logic, the frequency of this bug should significantly decrease, and any remaining occurrences will likely be chalked up to server side errors
According to the current build_recipe_v2.7.txt, librespot is being built from the sources at commit a4e0f58 which dates back to August. While it isn't clear from the github log just what issues the subsequent commits are likely to resolve, you could try building from the current sources on the master branch and see if you get a more-stable result.
I'm able to listen to Spotify for hours here---Spotify app on a iPad, moOde r4.4 on an RPi3B+ connected via WiFi, decent ISP connectivity via Verizon FiOS. Maybe I've just been lucky but I haven't run into the issue reported here.
Regards,
Kent
