You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error occurred in server:
× Thread 'screen' panicked.
├─▶ Originating Thread(s)
│ 1. screen_thread: HandlePtyBytes
│
├─▶ At /home/fuser/.cargo/registry/src/index.crates.io-6f17d22bba15001f/zellij-server-0.41.2/src/panes/grid.rs:1232:31
╰─▶ removal index (is 21) should be < len (is 17)
help: If you are seeing this message, it means that something went wrong.
>
-> To get additional information, check the log at: /tmp/zellij-1000/zellij-log/zellij.log
-> To see a backtrace next time, reproduce the error with: RUST_BACKTRACE=1 zellij [...]
-> To help us fix this, please open an issue: https://github.com/zellij-org/zellij/issues
Minimal reproduction
Happened once, don’t have a reproduction, sorry.
Other relevant information
It's on WSL in Windows Terminal.
But I was doing a compilation (long 100% CPU) in an IDE started in a zellij floating command. Was running low on battery => The PC started to get really slow. When it came back normal (compilation end) zellij started to react kind of normally, then crashed.
I bet Windows skipped sending some stuff between low battery, CPU at 100% charging/discharging on a random dock not from my laptop manufacturer.
The text was updated successfully, but these errors were encountered:
2. Issues with the Zellij
UI / behavior /crashIssue description
Minimal reproduction
Happened once, don’t have a reproduction, sorry.
Other relevant information
It's on WSL in Windows Terminal.
But I was doing a compilation (long 100% CPU) in an IDE started in a zellij floating command. Was running low on battery => The PC started to get really slow. When it came back normal (compilation end) zellij started to react kind of normally, then crashed.
I bet Windows skipped sending some stuff between low battery, CPU at 100% charging/discharging on a random dock not from my laptop manufacturer.
The text was updated successfully, but these errors were encountered: