mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #838] Crash when starting up with username #423
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#423
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 @hbbtstar on GitHub (Aug 29, 2021).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/838
Hey all!
I'm attempting to use librespot 0.2.0 (version string on startup is librespot 0.2.0 UNKNOWN (Built on 2021-08-28, Build ID: cETMHgxg)) and it's crashing on startup after authenticating: the stack trace is reproduced below with my username omitted.
I think it's something getting called in the session.rs file, since when I run the command without a username and password it doesn't crash and runs just fine.
I'm going to investigate more this week (including building an unstripped version of the library to demystify those stack traces) but I thought I'd open the ticket now to see if anybody had any initial directions to point me in. Thanks!
@roderickvd commented on GitHub (Aug 29, 2021):
Not at this point, the full stack trace of a debug build would be helpful.
@hbbtstar commented on GitHub (Aug 29, 2021):
so I think actually the crash was on attempting to play a song, not on startup: I got this stack trace when I started up with a debug build:
I rebooted the dev kit and it seemed to clear out whatever old stream was stuck in memory (I'm guessing, since the error appears to be related to bad timestamps) has been resolved! Closing this out as everything is working correctly now
@roderickvd commented on GitHub (Aug 29, 2021):
Thanks for the feedback, glad to hear it's working.