[Bug]:Google Drive crashes when Sync 'main' panicked at src/launch.rs:2489:33:
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 -
Installation Source
Flatpak
What version of Celeste are you using?
0.8.3
Storage Provider
Google Drive
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 -
same error.
Same error for me.
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:
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 -
Note: I was eventually able to get a sync but it was only on 200MB of stuff and crashed more than 7 times
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.