starred/komorebi
1
0
Fork 0
mirror of https://github.com/LGUG2Z/komorebi.git synced 2026-01-11 14:40:25 +01:00
Code Issues 87 Packages Projects Releases 10 Wiki Activity

[BUG]: After the v0.1.14 version, sometimes the program will freeze. #161

New Issue
Closed
opened 2026-01-05 14:48:38 +01:00 by adam · 11 comments
adam commented 2026-01-05 14:48:38 +01:00
Owner
Copy Link

Originally created by @MasouShizuka on GitHub (Nov 12, 2022).

Describe the bug
After the v0.1.14 version, sometimes the program freezes during use. Maybe this can't be called freeze, after all the program is not stuck, but the click and keyboard input are unresponsive, until after a while.

This phenomenon often occurs on vscode on my computer. I don't know if it is the cause of komorebi, but when it freezes, vscode will recover immediately after closing komorebi.

To Reproduce
Sorry, I don't know how to reproduce because I don't know the reason for this phenomenon.

Originally created by @MasouShizuka on GitHub (Nov 12, 2022). **Describe the bug** After the v0.1.14 version, sometimes the program freezes during use. Maybe this can't be called freeze, after all the program is not stuck, but the click and keyboard input are unresponsive, until after a while. This phenomenon often occurs on `vscode` on my computer. I don't know if it is the cause of `komorebi`, but when it freezes, `vscode` will recover immediately after closing `komorebi`. **To Reproduce** Sorry, I don't know how to reproduce because I don't know the reason for this phenomenon.
adam added the bug label 2026-01-05 14:48:38 +01:00
adam closed this issue 2026-01-05 14:48:38 +01:00
adam commented 2026-01-05 14:48:39 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Nov 12, 2022):

Thanks for the report! If you can try to capture a video of this happening it might help. 🙏

@LGUG2Z commented on GitHub (Nov 12, 2022): Thanks for the report! If you can try to capture a video of this happening it might help. 🙏
adam commented 2026-01-05 14:48:39 +01:00
Author
Owner
Copy Link

@MasouShizuka commented on GitHub (Nov 12, 2022):

Unfortunately, because I don't know when this phenomenon will happen, it may be difficult to record it.
But I will give it a try.

@MasouShizuka commented on GitHub (Nov 12, 2022): Unfortunately, because I don't know when this phenomenon will happen, it may be difficult to record it. But I will give it a try.
adam commented 2026-01-05 14:48:39 +01:00
Author
Owner
Copy Link

@MasouShizuka commented on GitHub (Nov 12, 2022):

Okay, after a bit of trying, I finally recorded it.

https://user-images.githubusercontent.com/44764707/201482517-7de23b28-8697-4d2b-bd78-73abb28b610f.mp4

@MasouShizuka commented on GitHub (Nov 12, 2022): Okay, after a bit of trying, I finally recorded it. https://user-images.githubusercontent.com/44764707/201482517-7de23b28-8697-4d2b-bd78-73abb28b610f.mp4
adam commented 2026-01-05 14:48:39 +01:00
Author
Owner
Copy Link

@GrewHair commented on GitHub (Nov 27, 2022):

+1 I've had same issues on 0.1.14, but with a web browser (Vivaldi), and Windows Terminal. Interestingly, the only inputs the "frozen" windows responded to in my case were touchpad scrolling (scrolling with mousewheel didn't work).

Rolling back to 0.1.13 eliminated the problem.

@GrewHair commented on GitHub (Nov 27, 2022): +1 I've had same issues on 0.1.14, but with a web browser (Vivaldi), and Windows Terminal. Interestingly, the only inputs the "frozen" windows responded to in my case were touchpad scrolling (scrolling with mousewheel didn't work). Rolling back to 0.1.13 eliminated the problem.
adam commented 2026-01-05 14:48:39 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Nov 27, 2022):

It's been a while and I'm unfortunately still unable to reproduce this. 😞

For anyone who is able to reproduce this behaviour, if you can run various builds from the commits between the latest release and the last release to help narrow down the exact commit that introduced this bug, that would be a big help. 🤞

@LGUG2Z commented on GitHub (Nov 27, 2022): It's been a while and I'm unfortunately still unable to reproduce this. 😞 For anyone who is able to reproduce this behaviour, if you can run various builds from the commits between the latest release and the last release to help narrow down the exact commit that introduced this bug, that would be a big help. 🤞
adam commented 2026-01-05 14:48:39 +01:00
Author
Owner
Copy Link

@Vernetzt commented on GitHub (Dec 6, 2022):

Going to chime in and say that I have also seen a return of this problem as well. VSCode does seem to be the most common problem window for me but I have seen it happen with Firefox, Explorer and a few others.

I think 5a0ba4cdbb was what ended up fixing it last time but not quite sure when it showed up again. I will say that it is definitely less frequent and much harder for me to reproduce unlike last time but my experience lines up with what was discussed on discord back in August and what is shown here.

The window will become unresponsive to input but if I move another window or kill komorebi it will cause the "frozen" window to "catch up" to previous inputs. I'll try to grab a new video as well but it really is a lot harder to reproduce this time lol.

@Vernetzt commented on GitHub (Dec 6, 2022): Going to chime in and say that I have also seen a return of this problem as well. VSCode does seem to be the most common problem window for me but I have seen it happen with Firefox, Explorer and a few others. I think 5a0ba4cdbb8d14ebc152f61df6c3214d27426e15 was what ended up fixing it last time but not quite sure when it showed up again. I will say that it is definitely less frequent and much harder for me to reproduce unlike last time but my experience lines up with what was discussed on discord back in August and what is shown here. The window will become unresponsive to input but if I move another window or kill komorebi it will cause the "frozen" window to "catch up" to previous inputs. I'll try to grab a new video as well but it really is a lot harder to reproduce this time lol.
adam commented 2026-01-05 14:48:39 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Dec 8, 2022):

This sounds super frustrating, especially since it's so hard to reliably reproduce. The next time any of you see it, can you share the logs from the period where it was not possible to interact with the application?

@LGUG2Z commented on GitHub (Dec 8, 2022): This sounds super frustrating, especially since it's so hard to reliably reproduce. The next time any of you see it, can you share the logs from the period where it was not possible to interact with the application?
adam commented 2026-01-05 14:48:40 +01:00
Author
Owner
Copy Link

@calendulish commented on GitHub (Dec 27, 2022):

The window will become unresponsive to input but if I move another window or kill komorebi it will cause the "frozen" window to "catch up" to previous inputs.

I had exactly this behavior before. I found that what was causing this was another program. So I defined a float rule on that program and the problem was solved.

I didn't report it cause it's really hard to understand why this is happening, but I think this tip is valid, the freeze seems to occur due to another window, not the same program that freeze. At least in my case.

my suggestion to you would be to check what else is on your screen during the freeze, including the taskbar and everything (even hidden ones), to identify which program is causing it.

@calendulish commented on GitHub (Dec 27, 2022): > The window will become unresponsive to input but if I move another window ~or kill komorebi~ it will cause the "frozen" window to "catch up" to previous inputs. I had exactly this behavior before. I found that what was causing this was another program. So I defined a float rule on that program and the problem was solved. I didn't report it cause it's really hard to understand why this is happening, but I think this tip is valid, the freeze seems to occur due to another window, not the same program that freeze. At least in my case. my suggestion to you would be to check what else is on your screen during the freeze, including the taskbar and everything (even hidden ones), to identify which program is causing it.
adam commented 2026-01-05 14:48:40 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Jan 22, 2023):

To add to what ShyPixie has said, and based on the comment from Vernetzt, if this is being caused by another application, it will most likely be a processes that is being managed by komorebi.

There has been a fair bit of work on the repo since 0.1.14; if anyone experiencing this would like to try out the latest build from the master branch, it's possible that it may have disappeared just as magically as it reappeared in 0.1.14. 😅

@LGUG2Z commented on GitHub (Jan 22, 2023): To add to what ShyPixie has said, and based on the comment from Vernetzt, if this _is_ being caused by another application, it will most likely be a processes that is being managed by `komorebi`. There has been a fair bit of work on the repo since 0.1.14; if anyone experiencing this would like to try out the latest build from the `master` branch, it's possible that it may have disappeared just as magically as it reappeared in `0.1.14`. 😅
adam commented 2026-01-05 14:48:40 +01:00
Author
Owner
Copy Link

@gldanoob commented on GitHub (Feb 6, 2023):

The freezing often occurs when I minimize/reopen windows. They could also be stuck minimized. Can confirm I had no such issue switching to 0.1.13 for which the minimize command hadn't been implemented.

@gldanoob commented on GitHub (Feb 6, 2023): The freezing often occurs when I minimize/reopen windows. They could also be stuck minimized. Can confirm I had no such issue switching to `0.1.13` for which the `minimize` command hadn't been implemented.
adam commented 2026-01-05 14:48:40 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (May 12, 2024):

Closing for staleness, please re-open if this is still an issue in newer versions

@LGUG2Z commented on GitHub (May 12, 2024): Closing for staleness, please re-open if this is still an issue in newer versions
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.1.36
apps-behaving-badly
bug
bug
cannot-reproduce
documentation
enhancement
github_actions
i-am-stuck
i-will-definitely-work-on-this
i-will-not-work-on-this
i-will-probably-work-on-this
komorebi
komorebi-bar
komorebic
performance
pull-request
Mirrored from GitHub Pull Request
 translation
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/komorebi#161
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?