celeste icon indicating copy to clipboard operation
celeste copied to clipboard

[Bug]:Google Drive crashes when Sync 'main' panicked at src/launch.rs:2489:33:

Open JosiahFin opened this issue 10 months ago • 5 comments

Bug Description

When I attempt to sync google drive to a folder in my documents it crashes about 2 minutes into the process

thread 'main' panicked at src/launch.rs:2489:33: internal error: entered unreachable code stack backtrace: thread 'main' panicked at library/core/src/panicking.rs:221:5: panic in a function that cannot unwind stack backtrace: 0: 0x55b65200d905 - 1: 0x55b65203c5eb - 2: 0x55b652009ecf - 3: 0x55b65200d6de - 4: 0x55b65200ec29 - 5: 0x55b65200e9cc - 6: 0x55b65200f201 - 7: 0x55b65200f033 - 8: 0x55b65200ddc9 - 9: 0x55b65200ed44 - 10: 0x55b652039565 - 11: 0x55b6520395f2 - 12: 0x55b652039736 - 13: 0x55b650139f04 - 14: 0x703d911e191a - g_closure_invoke 15: 0x703d911f65c3 - 16: 0x703d911f8071 - 17: 0x703d911fde01 - g_signal_emit_valist 18: 0x703d911fdec3 - g_signal_emit 19: 0x703d902fe120 - 20: 0x703d902fe2d7 - g_application_run 21: 0x55b650002ec8 - 22: 0x55b6500aa0e7 - 23: 0x55b6501dda63 - 24: 0x55b6500ddc79 - 25: 0x55b652001782 - 26: 0x55b6500ad205 - 27: 0x703d8fdeb188 - 28: 0x703d8fdeb24b - __libc_start_main 29: 0x55b64ffc4025 - 30: 0x0 - thread caused non-unwinding panic. aborting.

Installation Source

Flatpak

What version of Celeste are you using?

0.8.3

Storage Provider

Google Drive

JosiahFin avatar Jan 28 '25 13:01 JosiahFin

I may be hitting the same error on my first attempt at using Celeste. Also attempting to sync to Google Drive, also using Flatpak Celeste. Error message:

thread 'main' panicked at src/launch.rs:2489:33: internal error: entered unreachable code stack backtrace: thread 'main' panicked at library/core/src/panicking.rs:221:5: panic in a function that cannot unwind stack backtrace: 0: 0x5ec9119ad905 - 1: 0x5ec9119dc5eb -

metawindow avatar Jan 29 '25 23:01 metawindow

same error.

JesusChapman avatar Feb 01 '25 20:02 JesusChapman

Same error for me.

euglevi avatar Feb 06 '25 16:02 euglevi

Same error here so I built from source and got a bit more detail (but I removed a 3 unnecessary rust features when I compiled):

`thread 'main' panicked at src/launch.rs:2489:33: internal error: entered unreachable code stack backtrace: 0: rust_begin_unwind 1: core::panicking::panic_fmt 2: core::panicking::panic 3: celeste::launch::launch::sync_remote_directory 4: celeste::launch::launch 5: <O as gio::auto::application::ApplicationExt>::connect_activate::activate_trampoline 6: g_closure_invoke 7: 8: 9: g_signal_emit_valist 10: g_signal_emit 11: 12: g_application_run 13: <O as gio::application::ApplicationExtManual>::run_with_args 14: celeste::main

thread 'main' panicked at library/core/src/panicking.rs:218:5: panic in a function that cannot unwind stack backtrace: 0: 0x5cf2e6498e50 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h9181978393d605cc 1: 0x5cf2e64c8fe3 - core::fmt::write::h1ebafd1030a45fea 2: 0x5cf2e6494b03 - std::io::Write::write_fmt::h2180fa86bf59ca23 3: 0x5cf2e6498ca2 - std::sys::backtrace::BacktraceLock::print::h249460249988fc24 4: 0x5cf2e6499d3f - std::panicking::default_hook::{{closure}}::h4a7de45ad1f07f4f 5: 0x5cf2e6499baa - std::panicking::default_hook::h3f2317e37d71fa77 6: 0x5cf2e649a762 - std::panicking::rust_panic_with_hook::hbd27a78b3490985e 7: 0x5cf2e649a4b6 - std::panicking::begin_panic_handler::{{closure}}::hd6305028d0015665 8: 0x5cf2e6499369 - std::sys::backtrace::__rust_end_short_backtrace::h39da8ae6bd6da52c 9: 0x5cf2e649a17d - rust_begin_unwind 10: 0x5cf2e64c5ecd - core::panicking::panic_nounwind_fmt::hb82d7cdb7ec1b361 11: 0x5cf2e64c5f62 - core::panicking::panic_nounwind::h377ba57c0a223578 12: 0x5cf2e64c6086 - core::panicking::panic_cannot_unwind::ha40c70a4a7358475 13: 0x5cf2e451fa12 - <O as gio::auto::application::ApplicationExt>::connect_activate::activate_trampoline::h129ae8af7c5750f7 14: 0x794f2c85a2fa - g_closure_invoke 15: 0x794f2c88990c - 16: 0x794f2c87a591 - 17: 0x794f2c87a7c1 - g_signal_emit_valist 18: 0x794f2c87a883 - g_signal_emit 19: 0x794f2b917690 - 20: 0x794f2b917823 - g_application_run 21: 0x5cf2e4469aa1 - <O as gio::application::ApplicationExtManual>::run_with_args::h055afd4930bb1f25 22: 0x5cf2e447037d - celeste::main::hbf6e2b8fa64aa0ea 23: 0x5cf2e444a583 - std::sys::backtrace::__rust_begin_short_backtrace::hd802d24644e98271 24: 0x5cf2e4624749 - std::rt::lang_start::{{closure}}::h99ac7deba789b516 25: 0x5cf2e648be90 - std::rt::lang_start_internal::h3b92f582fcef7b5a 26: 0x5cf2e4472ee5 - main 27: 0x794f2b22a1ca - __libc_start_call_main at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16 28: 0x794f2b22a28b - __libc_start_main_impl at ./csu/../csu/libc-start.c:360:3 29: 0x5cf2e4430365 - _start 30: 0x0 - thread caused non-unwinding panic. aborting.`

Note: I was eventually able to get a sync but it was only on 200MB of stuff and crashed more than 7 times

Nick-Henkey avatar Feb 07 '25 21:02 Nick-Henkey

I noticed something about this that should be taken into account. I had the same thing happen with a folder called Takeout, there were two such folders (which no local file system is able to support, and for obvious reasons). I didn't need what was in either of them, so I trashed them and emptied. Retrying to see if that has anything to do with it.

daebreaker avatar May 09 '25 23:05 daebreaker