-
Notifications
You must be signed in to change notification settings - Fork 657
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
Panic: source slice length (16) does not match destination slice length (20)
#1188
Comments
Please provide version information. |
Sorry I forgot, this was the dev branch at the time I made the issue. |
It sometimes happens that the packet isn’t received fully. I thought I had made that piece of the code panic-free but I guess I missed something. |
Got a new stack trace:
As the stack trace says, this is librespot f037e46. I will try to get a stacktrace with debugging information next. |
Other than that it would be nice to make it panic-free, I see at the beginning of the log that it fails to bind, that the address is already in use? |
I'm not sure why that is. Maybe I was running another librespot instance at the same time, or maybe it's because I have a WireGuard network interface too that librespot doesn't seem to like very much. (I have now switched to libespot-java because that's the only thing that will work correctly on my network, feel free to close this if there is nothing important to fix). |
same bug with this episode |
ye it works with Java not Rust for some reason |
Does still happen on latest dev? There have been a lot of improvements there since. |
I don't know, I've switched to go-librespot which works reliably for me right now. |
Gonna close then, if you don't expect to provide further feedback. |
@roderickvd it still error here is how i fix it ( sory this repo has been hardly modify fron core so i can not push it to here ) |
Cool, thanks! I'll remember to push a commit for it manually. |
…acks Fixes #1188 Co-authored-by: thedtvn <[email protected]>
Just put in your fix @thedtvn with a small change. Since I don't have a Spotify account anymore, could someone test before I put out a 0.6.0 release? |
Describe the bug
After running for a while, librespot crashes with a huge stacktrace.
To reproduce
I don't know, I think I just left it running for a few hours. Note that my internet connection is weird (see Spotifyd/spotifyd#1211) so that might have something to do with it.
I am hopeful though that the stack trace provides enough clues as to why it crashes.
I'll provide additional information if it happens again.
Log
No full log, but here is the stack trace:
Host (what you are running
librespot
on):Additional context
Weirdly, librespot just continued running after what looks like a fatal error to me. From the log it appears that I was trying to start playing some music (which didn't last long due to Spotifyd/spotifyd#1211).
The text was updated successfully, but these errors were encountered: