Originally created by @topazrn on GitHub (Jul 24, 2024).
Describe the bug
CPU usage is around 20% on my i3-12100 and disk usage is 4MB/s while idle. I'm not sure if this is normal.
I have made sure that I did not enable the custom FFM implementation because if I were to use it, my CPU usage would double.
To Reproduce
Steps to reproduce the behavior:
komorebic start --ahk.
Check Task Manager.
Expected behavior
CPU usage I think should be 0% on idle. I'm also not sure what file is it reading constantly.
Operating System
OS Name: Microsoft Windows 10 Pro
OS Version: 10.0.19045 N/A Build 19045
komorebic check Output
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\Topaz
Looking for configuration files in C:\Users\Topaz
Found komorebi.json; this file can be passed to the start command with the --config flag
No ~/.config/whkdrc found; you may not be able to control komorebi with your keyboard
Additional context
I am using the example AHK config from the docs. But I think AHK is not the problem here because the CPU and disk usage are undiscernable between AHK and whkd.
Originally created by @topazrn on GitHub (Jul 24, 2024).
**Describe the bug**
CPU usage is around 20% on my i3-12100 and disk usage is 4MB/s while idle. I'm not sure if this is normal.

I have made sure that I did not enable the custom FFM implementation because if I were to use it, my CPU usage would double.

**To Reproduce**
Steps to reproduce the behavior:
1. `komorebic start --ahk`.
2. Check Task Manager.
**Expected behavior**
CPU usage I think should be 0% on idle. I'm also not sure what file is it reading constantly.
**Operating System**
```
OS Name: Microsoft Windows 10 Pro
OS Version: 10.0.19045 N/A Build 19045
```
**`komorebic check` Output**
```
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\Topaz
Looking for configuration files in C:\Users\Topaz
Found komorebi.json; this file can be passed to the start command with the --config flag
No ~/.config/whkdrc found; you may not be able to control komorebi with your keyboard
```
**Additional context**
I am using the example AHK config from the docs. But I think AHK is not the problem here because the CPU and disk usage are undiscernable between AHK and whkd.
adam
added the bug label 2026-01-05 14:50:44 +01:00
The high disk IO suggests that there are probably a bunch of errors being written to the log file repeatedly. Can you run komorebi.exe in the foreground and share the log output?
@LGUG2Z commented on GitHub (Jul 24, 2024):
The high disk IO suggests that there are probably a bunch of errors being written to the log file repeatedly. Can you run `komorebi.exe` in the foreground and share the log output?
Aha! You are right! Turns out it has been repeatedly throwing these errors:
2024-07-24T13:19:25.499291Z INFO komorebi::border_manager: listening
2024-07-24T13:19:25.499592Z WARN komorebi::border_manager: restarting failed thread: The parameter is incorrect. (0x80070057)
I was following amnweb's dotfiles and it seems removing "border_implementation": "Windows", fixes the issue.
I should've checked the logs first before writing an issue. Thanks for the help!
@topazrn commented on GitHub (Jul 24, 2024):
Aha! You are right! Turns out it has been repeatedly throwing these errors:
```
2024-07-24T13:19:25.499291Z INFO komorebi::border_manager: listening
2024-07-24T13:19:25.499592Z WARN komorebi::border_manager: restarting failed thread: The parameter is incorrect. (0x80070057)
```
I was following amnweb's dotfiles and it seems removing `"border_implementation": "Windows",` fixes the issue.
I should've checked the logs first before writing an issue. Thanks for the help!
So this option isn't supported on Win10 and there are some checks in place to stop people from trying to enable it once komorebi is running, but I think we need to default away from this option on startup if it is selected to avoid the experience you had 🤔
@LGUG2Z commented on GitHub (Jul 24, 2024):
So this option isn't supported on Win10 and there are some checks in place to stop people from trying to enable it once komorebi is running, but I think we need to default away from this option on startup if it is selected to avoid the experience you had 🤔
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @topazrn on GitHub (Jul 24, 2024).
Describe the bug

CPU usage is around 20% on my i3-12100 and disk usage is 4MB/s while idle. I'm not sure if this is normal.
I have made sure that I did not enable the custom FFM implementation because if I were to use it, my CPU usage would double.

To Reproduce
Steps to reproduce the behavior:
komorebic start --ahk.Expected behavior
CPU usage I think should be 0% on idle. I'm also not sure what file is it reading constantly.
Operating System
komorebic checkOutputAdditional context
I am using the example AHK config from the docs. But I think AHK is not the problem here because the CPU and disk usage are undiscernable between AHK and whkd.
@LGUG2Z commented on GitHub (Jul 24, 2024):
The high disk IO suggests that there are probably a bunch of errors being written to the log file repeatedly. Can you run
komorebi.exein the foreground and share the log output?@topazrn commented on GitHub (Jul 24, 2024):
Aha! You are right! Turns out it has been repeatedly throwing these errors:
I was following amnweb's dotfiles and it seems removing
"border_implementation": "Windows",fixes the issue.I should've checked the logs first before writing an issue. Thanks for the help!
@LGUG2Z commented on GitHub (Jul 24, 2024):
So this option isn't supported on Win10 and there are some checks in place to stop people from trying to enable it once komorebi is running, but I think we need to default away from this option on startup if it is selected to avoid the experience you had 🤔