-
-
Notifications
You must be signed in to change notification settings - Fork 658
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
When destroying multiple windows at once using cmd+q, all defined signals are automatically removed #1965
Comments
Sounds like a crash. Check Console.app for a log. |
yabai-v6.0.0
|
Right I see what the issue is. Need to think a bit to decide how to solve this. Nvm, it is not the issue I thought it was. Unable to reproduce as well in both debug and release mode. |
I believe this should be fixed on master, but as I cannot reproduce the original problem I am unable to verify the fix. |
I'll try the master branch and report back here |
I tried to open 50 kitty, but kitty couldn’t hold it anymore and reported an error, hahaha Yabai is performing very well. I can confirm that the master branch has fixed this issue. ❯ wc -l /tmp/close-kitty.log
50 /tmp/close-kitty.log Thank you for your quick fix! |
Defined signals for window_destroyed events
Opened a 20+ kitty(new window) windows
Used cmd+q on one of the kitty windows
All windows were destroyed, but the window_destroyed was only triggered 9 times
And all defined signals were deleted by yabai -m signal --list checking
The text was updated successfully, but these errors were encountered: