Crash on vim mode: `/src/input.cpp:367: failed assertion: event_storage_.empty() && "event_storage_ should be empty"`

[TonalidadeHidrica]

Crash on vim mode: `/src/input.cpp:367: failed assertion: event_storage_.empty() && "event_storage_ should be empty"`

[zanchey]

If you can install the fish-dbgsym package, I think you'll at least get symbols, though it's pretty clear where this assert is firing.

[mqudsi]

If you don't have a reproducer, it would be best if you could build and install the latest release. We still have that assertion in the now-rust codebase, so the bug could still be present.

[mqudsi]

Yup.

[TonalidadeHidrica]

I'll do that and tell you results once I get them. But after all, asking just in case, is it useful? I guess the next version will be the rewritten-in-Rust release. Now that the code is rewirtten, the bug may not exist in the next release.

[krobelus]

a deterministic reproducer would be great. It might be fixed in latest master but we don't know yet. With a reproducer that's easy to test

[TonalidadeHidrica]

You mean from the master branch instead of 3.7.1 tag?

[krobelus]

This is fixed since the new logic keeps self.event_storage always empty (only the heap allocation is reused but only after being swapped into a local variable).
If it is decided that we have a patch release then we can add it