Open musshorn opened 1 year ago
Is this always around 3 hours (and how much exactly)? Strange because I certainly have had longer-than-3-hour listening sessions and not experienced this before.
From the above I see the token is refreshed twice on almost the same second. This leads me to believe there may be a race condition, getting the two tokens in parallel. This may indeed by the case as preloaded threads run in parallel and don't wait when one or the other is getting the token already.
I don't have time to do it, but anyone inclined may try to fix this in spclient
by locking a mutex or maybe a Condvar
with timeout may be even better to prevent starvation.
I'm not sure that it's always around 3 hours? but it's happened a few times and always seems to have issues after an extended period of listening. How long do the session tokens last for?
One hour and we refresh them a little while before that just to be sure.
With a full log or at least start and end you can see the interval how long it lasted for you.
Describe the bug After around 3 hours of playback, it just stops completely and every song becomes unplayable. Looking at the logs there seems to be a lot of 403 errors appearing.
To reproduce Steps to reproduce the behavior:
Log A full log so we may trace your problem (launch
librespot
with--verbose
). Format the log as code. This is the section leading up to the failures. Full log is 1.3mb of mostly working completely fine so I don't know if you want all that.That pattern of an increasing number of tracks failing continues until it's looped through the whole playlist (I assume that's what the position X of 73 is)
Host (what you are running
librespot
on):