thread 'main' panicked at helix-core/src/transaction.rs:499:9:

[ElYaiko]

Summary

Helix crashes

Reproduction Steps

I was writing and it crashed

Helix log

thread 'main' panicked at helix-core/src/transaction.rs:499:9:
Positions [(2944, BeforeSticky)] are out of range for changeset len 2943!
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Platform

Linux

Terminal Emulator

st-256color

Installation Method

source

Helix Version

helix 24.7 (be2884d)

[the-mikedavis]

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

[aral]

Just ran into this on latest macOS, running Helix under WesTerm.

Although the error message is ever so slightly different (same line/column):

thread 'main' panicked at helix-core/src/transaction.rs:499:9:
  Positions [(1318, AfterSticky), (1331, BeforeSticky)] are out of range for changeset

Unfortunately, no backtrace as it’s a random crash and I wasn’t already running with RUST_BACKTRACE=1. Is there any way to get a backtrace after the fact to help diagnose random crashes like this (or should we always be running with the backtrace option?)

[the-mikedavis]

There isn't a way to go back and salvage a backtrace AFAIK. You can set RUST_BACKTRACE=1 or RUST_BACKTRACE=full globally so if there is a panic you see a backtrace. For this bug though I suspect the backtrace might not be enough to figure out the cause - for this one we might need a reproduction case or an idea of what the last few commands executed were

[RGBCube]

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.

[simplicity-load]

Hello everyone, so this happened twice just today so I turned the Backtrace option on after the first occurrence and got a fuller stacktrace:

thread 'main' panicked at helix-core/src/transaction.rs:499:9:
Positions [(652, AfterSticky), (653, BeforeSticky)] are out of range for changeset len 542!
stack backtrace:
   0:     0x588fd458d4d6 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::haad32dbdee93b0c8
   1:     0x588fd36cb223 - core::fmt::write::h6ad3ba0dedbcf173
   2:     0x588fd456195f - std::io::Write::write_fmt::ha3ff7d1996e99b72
   3:     0x588fd458d323 - std::sys::backtrace::BacktraceLock::print::hb6e0ad5a95b804a0
   4:     0x588fd45822ce - std::panicking::default_hook::{{closure}}::hdde2e5ae82f46e0d
   5:     0x588fd4582193 - std::panicking::default_hook::h24772f302d635910
   6:     0x588fd4582898 - std::panicking::rust_panic_with_hook::h89de30867df48bb1
   7:     0x588fd458d9ea - std::panicking::begin_panic_handler::{{closure}}::h98d82b909a800684
   8:     0x588fd458d6d9 - std::sys::backtrace::__rust_end_short_backtrace::h0b5e9482c92da20f
   9:     0x588fd458236d - __rustc[b723cc1e8dfe1f7e]::rust_begin_unwind
  10:     0x588fd35da030 - core::panicking::panic_fmt::he852a8970ea4b64e
  11:     0x588fd397f516 - helix_core::transaction::ChangeSet::update_positions::h71a895aae2c5516b
  12:     0x588fd42298fe - helix_view::view::View::apply::ha6fa2c3690d3f8fe
  13:     0x588fd424fadc - helix_view::document::Document::append_changes_to_history::h2e2739cb4f188006
  14:     0x588fd3f94794 - <helix_term::ui::editor::EditorView as helix_term::compositor::Component>::handle_event::hae620b2ebcaf1f4b
  15:     0x588fd40f52be - helix_term::compositor::Compositor::handle_event::h97bfb3015a30cb6b
  16:     0x588fd4318fb5 - hx::main_impl::{{closure}}::h084fe50293a2e418
  17:     0x588fd43156e4 - tokio::runtime::park::CachedParkThread::block_on::h68c9e0ef0059e27c
  18:     0x588fd439261a - tokio::runtime::context::runtime::enter_runtime::ha5aae49322a5abdd
  19:     0x588fd4345d7c - tokio::runtime::runtime::Runtime::block_on::h2f85636c23921fe8
  20:     0x588fd43a275d - hx::main::h23bc16d8952799fc
  21:     0x588fd437d476 - std::sys::backtrace::__rust_begin_short_backtrace::h1b81122e3468afe5
  22:     0x588fd4393431 - std::rt::lang_start::{{closure}}::h9088c525606d0b70
  23:     0x588fd455ee46 - std::rt::lang_start_internal::hd068bdda00676a8c
  24:     0x588fd43a284d - main
  25:     0x7637dfa2a4d8 - __libc_start_call_main
  26:     0x7637dfa2a59b - __libc_start_main_impl
  27:     0x588fd3644135 - _start
  28:                0x0 - <unknown>

I'll try to reproduce but here's the last steps I took up right before the crash so I don't forget them:
Working setup:

helix 25.07.1 (happened on 25.01, previous version aswell)

Mostly working on go files so heres the language servers:

Configured language servers:
  ✓ gopls: /nix/store/dyq17gi1j5ra1qrga0ny1cbhblc1lp76-gopls-0.18.1/bin/gopls
  ✓ golangci-lint-lsp: /nix/store/qa21d44i4fviyphav6ldxib9m441ngmw-golangci-lint-langserver-0.0.11/bin/golangci-lint-langserver
Configured debug adapter:
  ✓ /nix/store/jkx7svr17zvnnc1m736ipi2jnw71w5ii-delve-1.24.2/bin/dlv
Configured formatter: None
Tree-sitter parser: ✓
Highlight queries: ✓
Textobject queries: ✓
Indent queries: ✓

Setup:

1. Make edits to some go source generated file
2. I think I didn't save the modified generated file
3. Rerun the generation
4. Run reload-all
5. Move around or maybe save
6. BOOM

Will report back if I reproduce