Skip to content
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

crash after playback ends #196

Closed
jurafxp opened this issue Mar 25, 2018 · 1 comment · Fixed by #206
Closed

crash after playback ends #196

jurafxp opened this issue Mar 25, 2018 · 1 comment · Fixed by #206
Labels

Comments

@jurafxp
Copy link

jurafxp commented Mar 25, 2018

Hello,
when the playback ends, librespot always crashes with following message:

 thread 'main' panicked at 'Box<Any>', core/src/session.rs:79:42
 stack backtrace:
    0:     0x5649b9f3422f - std::sys::imp::backtrace::tracing::imp::unwind_backtrace::h124b4bcef8>
    1:     0x5649b9f1a0f1 - std::sys_common::backtrace::print::hc582a11b3ee21b31
    2:     0x5649b9f2562d - std::panicking::default_hook::{{closure}}::h8186675e6f93fe64
    3:     0x5649b9f252df - std::panicking::default_hook::hd0d178fcebd87257
    4:     0x5649b9f25b1d - std::panicking::rust_panic_with_hook::h3ecd70e9e7b4a365
    5:     0x5649b9c7649a - std::panicking::begin_panic_new::hb538b624dc78c62a
    6:     0x5649b9cb5857 - <futures::future::map_err::MapErr<A, F> as futures::future::Future>::>
    7:     0x5649b9ef903c - tokio_core::reactor::Core::poll::h26ce83ebe657b45c
    8:     0x5649b9b8ffa4 - librespot::main::h9e79c76471055a88
    9:     0x5649b9f3c6e7 - __rust_maybe_catch_panic
   10:     0x5649b9f257c7 - std::panicking::try::h36ff7733b5113eb6
   11:     0x5649b9f36269 - std::rt::lang_start::h60bbe14d465df98b
   12:     0x7f2b65551f69 - __libc_start_main
   13:     0x5649b9b72299 - _start
   14:                0x0 - <unknown>

I have tried to build the latest master with same results.
Parameters for build:

 cargo build --release --no-default-features --features alsa-backend
@sashahilton00
Copy link
Member

Difficult to say what this is exactly, though I expect it's to do with #134 seeing as it looks like all the other errors related to reconnection. Will leave this open for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants