thread 'main' panicked at helix-core/src/transaction.rs:499:9: #11968
Replies: 6 comments 1 reply
-
|
Without a backtrace or reproduction case it's impossible to tell what's the cause. If you can find a way to reproduce this reliably please post the steps |
Beta Was this translation helpful? Give feedback.
-
|
Just ran into this on latest macOS, running Helix under WesTerm. Although the error message is ever so slightly different (same line/column): Unfortunately, no backtrace as it’s a random crash and I wasn’t already running with |
Beta Was this translation helpful? Give feedback.
-
|
Just ran into this myself, but couldn't figure out a way to reproduce either. I'll run helix with RUST_BACKTRACE=1 from now on and report if I run into this again. |
Beta Was this translation helpful? Give feedback.
-
|
Hello everyone, so this happened twice just today so I turned the Backtrace option on after the first occurrence and got a fuller stacktrace: I'll try to reproduce but here's the last steps I took up right before the crash so I don't forget them: Mostly working on go files so heres the language servers: Setup:
Will report back if I reproduce |
Beta Was this translation helpful? Give feedback.
-
|
Hi everyone, same thing happened to me just now.
I was working on a rust project without running rust-analyzer ( I'll run helix with RUST_BACKTRACE=1 from now on just like #11968 (comment), and report if I run into this again. |
Beta Was this translation helpful? Give feedback.
-
|
Just got another crash: thread 'main' (8667166) panicked at helix-core/src/transaction.rs:499:9:
Positions [(6490, AfterSticky), (6491, BeforeSticky)] are out of range for changeset len 6364!
stack backtrace:
0: 0x10165b8ec - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h129f08280ae8688e
1: 0x100955c28 - core::fmt::write::h379b538a6cc1b313
2: 0x10163d094 - std::io::Write::write_fmt::he3a2ffb8251ded46
3: 0x1016570c4 - std::sys::backtrace::BacktraceLock::print::hce3c8ef93ddb05ce
4: 0x10163e644 - std::panicking::default_hook::{{closure}}::h587b43a4877e76d5
5: 0x10163e314 - std::panicking::default_hook::h79b9005ca4003ceb
6: 0x10163e920 - std::panicking::panic_with_hook::h37156b8e1e9b0760
7: 0x10165983c - std::panicking::panic_handler::{{closure}}::h062168c38b198d14
8: 0x1016571d0 - std::sys::backtrace::__rust_end_short_backtrace::h8081e45189cd9348
9: 0x10163bcfc - __rustc[bd3b3f48d2381c32]::rust_begin_unwind
10: 0x10171a8e8 - core::panicking::panic_fmt::h018a203419754807
11: 0x100bf5120 - helix_core::transaction::ChangeSet::update_positions::h3b846ecfc0634608
12: 0x1013cdfbc - helix_view::view::View::apply::h36507eb4626ab2e4
13: 0x1013cb210 - helix_view::view::View::sync_changes::hf6bb2891b18284b2
14: 0x101377cf0 - helix_view::editor::Editor::focus::hbf114f8ac0ed96a8
15: 0x10124449c - <helix_term::ui::editor::EditorView as helix_term::compositor::Component>::handle_event::h1fc2dbdcd96eead4
16: 0x1011d2560 - helix_term::compositor::Compositor::handle_event::h5b0e70dfe5ab6f4c
17: 0x10142296c - hx::main_impl::{{closure}}::h4b263d8b7d62cca9
18: 0x10142e8f0 - tokio::runtime::park::CachedParkThread::block_on::h6c99b11fd1e561e6
19: 0x1014697b4 - tokio::runtime::context::runtime::enter_runtime::h1f830f1fe184d478
20: 0x10148dad0 - tokio::runtime::runtime::Runtime::block_on::hda0184522938780f
21: 0x101473498 - hx::main::hbd0a7b6d1414fc90
22: 0x10148686c - std::sys::backtrace::__rust_begin_short_backtrace::haf5908caf81f808e
23: 0x101481304 - std::rt::lang_start::{{closure}}::h29f1d3ed265fbabc
24: 0x101628aa4 - std::rt::lang_start_internal::h652a768977fc55ea
25: 0x10147d830 - _main |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
Helix crashes
Reproduction Steps
I was writing and it crashed
Helix log
Platform
Linux
Terminal Emulator
st-256color
Installation Method
source
Helix Version
helix 24.7 (be2884d)
Beta Was this translation helpful? Give feedback.
All reactions