Send-to-monitor sometimes causes panics #31

New Issue

2026-01-05T14:47:49+01:00

adam commented

2026-01-05 14:47:49 +01:00

Originally created by @OxleyS on GitHub (Sep 18, 2021).

Originally assigned to: @LGUG2Z on GitHub.

On release 0.1.4. Not sure how sure-fire this repro is:

Have a single window open on each of two monitors
komorebic start
Use send-to-monitor to send the window on monitor 0 to monitor 1

This seems to cause a panic. From komorebic log:

ERROR read_commands:process_command{SendContainerToMonitorNumber(0)}:move_container_to_monitor{idx=0 follow=false}: komorebi: panicked at 'removal index (is 0) should be < len (is 0)', library\alloc\src\vec\mod.rs:1378:13 panic.file="library\\alloc\\src\\vec\\mod.rs" panic.line=1378 panic.column=13

Once this panic happens, Komorebi stops responding to komorebic commands and has to be killed manually with Task Manager.

Originally created by @OxleyS on GitHub (Sep 18, 2021). Originally assigned to: @LGUG2Z on GitHub. On release 0.1.4. Not sure how sure-fire this repro is: 1. Have a single window open on each of two monitors 2. `komorebic start` 3. Use `send-to-monitor` to send the window on monitor 0 to monitor 1 This seems to cause a panic. From `komorebic log`: ``` ERROR read_commands:process_command{SendContainerToMonitorNumber(0)}:move_container_to_monitor{idx=0 follow=false}: komorebi: panicked at 'removal index (is 0) should be < len (is 0)', library\alloc\src\vec\mod.rs:1378:13 panic.file="library\\alloc\\src\\vec\\mod.rs" panic.line=1378 panic.column=13 ``` Once this panic happens, Komorebi stops responding to `komorebic` commands and has to be killed manually with Task Manager.

adam added the bug label 2026-01-05 14:47:49 +01:00

adam closed this issue

2026-01-05 14:47:49 +01:00

adam commented

2026-01-05 14:47:49 +01:00

@LGUG2Z commented on GitHub (Sep 18, 2021):

Thanks for sharing the panic message! Can you try running komorebi from this branch and see if it solves the issue? If you don't have a Rust toolchain set up, you can grab the binaries from the artifacts saved by this GitHub Actions workflow run.

@LGUG2Z commented on GitHub (Sep 18, 2021): Thanks for sharing the panic message! Can you try running komorebi from [this branch](https://github.com/LGUG2Z/komorebi/compare/hotfix/send-to-monitor-panic) and see if it solves the issue? If you don't have a Rust toolchain set up, you can grab the binaries from the artifacts saved by [this GitHub Actions workflow run](https://github.com/LGUG2Z/komorebi/actions/runs/1249187720).

adam commented

2026-01-05 14:47:49 +01:00

@LGUG2Z commented on GitHub (Sep 18, 2021):

Stop-Process -Name komorebi

This is also a nice quick way to kill the process from Powershell if you run into panics again ^

@LGUG2Z commented on GitHub (Sep 18, 2021): ```powershell Stop-Process -Name komorebi ``` This is also a nice quick way to kill the process from Powershell if you run into panics again ^

adam commented

2026-01-05 14:47:50 +01:00

@OxleyS commented on GitHub (Sep 19, 2021):

That seems to have done the trick! I played around with it for a while and wasn't able to make the panic happen again.

@OxleyS commented on GitHub (Sep 19, 2021): That seems to have done the trick! I played around with it for a while and wasn't able to make the panic happen again.

adam commented

2026-01-05 14:47:50 +01:00

@LGUG2Z commented on GitHub (Sep 19, 2021):

Great! This fix is now in the master branch and will be included in the next release.

@LGUG2Z commented on GitHub (Sep 19, 2021): Great! This fix is now in the `master` branch and will be included in the next release.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/komorebi#31