-
-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed windows are not removed from the tree on macOS 15 Sequoia #471
Comments
Can't reporduce in macos |
@nikitabobko Thank you for testing! I upgraded to macOS 15.1 beta 3 and reinstalled AeroSpace, but the issue continued. I then quit all running apps and background processes, and I found that the Contexts app was causing the problem. If anyone else has this issue, quit Contexts and restart AeroSpace to fix it. |
Same issue here. I'm on |
My approach was to: (a) close all running applications, (b) close all menu bar apps, and (c) use Activity Monitor to end all background processes from third-party apps. Eventually, I identified the problem, which was Contexts in my case. |
Thanks Felix! I forgot to consider my menu bar apps. After debugging, it was Amazon Q that's causing the issue in my case. But it's worth noting that prior to the OS update, both apps were working in harmony. I noticed that is the case for your app as well. So what could be causing such a conflict? Because not using some app is more of a workaround than a fix. What our apps have in common is that they both install an overlay, which somehow interferes with how Aerospace detects active windows? Bottom line is I think this issue should remain open because Aerospace should work regardless of what app you have open. |
To my knowledge, Aerospace utilizes Apple's accessibility API to detect and manage windows. Sequoia has implemented several changes to this API, which has caused problems for window managers like Amethyst. Unfortunately, I am not familiar enough with this API to identify the exact issue. It might be possible to reproduce the problem using a demo app in Xcode by comparing the list of windows reported by the accessibility API before and after closing a window. This could then be reported to the developers of the affected apps. The Contexts app hasn't been updated for several years, so I have now switched to an alternative. |
The yabai window manager experienced the same issue when using Contexts or Amazon Q (Issue 2324, Issue 2431). A potential fix has been implemented (Commit). Perhaps this workaround could also be applied to AeroSpace, @nikitabobko? |
yabai uses private APIs in their commit. I think that it's possible to circumvent this Sequoia bug using public APIs. My solution is described in #445 |
Hey @FelixLisczyk , I also use currently use Contexts app for MacOS, but it's buggy with AeroSpace. What alternative have you switched to? |
@jsonMartin I'm using AeroSpace and the Raycast window switcher to organize my windows. This issue is currently being worked on in #445, so it may work better with the Contexts app in the future. |
Thanks! Funny you mention that, I also use Raycast and found the Switch Windows command. I migrated over from Contexts, and it works just about as well for application switching. Happy to remove one piece of redundant software from my stack; and it also works much better with AeroSpace. I combined the above with AltTab for thumbnails and am happy with the result! |
I'm using Aerospace v0.14.2-Beta on the latest macOS 15 beta (24A5331b). When I close a window, it remains in the tree hierarchy and still takes up part of the screen. This issue does not occur on my macOS 14 installation.
Steps to Reproduce
Expected Result
The first Finder window should fill the entire display.
Actual Result
The first Finder window does not expand to fill the entire display.
Additional Notes
This issue also occurs with other applications.
Here is the output of
aerospace list-windows --workspace visible
after closing the second Finder window:Console output of
aerospace debug-windows
: debug-windows.txtChecklist
The text was updated successfully, but these errors were encountered: