search

nikitabobko / AeroSpace

AeroSpace is an i3-like tiling window manager for macOS
https://nikitabobko.github.io/AeroSpace/guide
MIT License
5.64k stars 89 forks source link

Closed windows are not removed from the tree on macOS 15 Sequoia #471

Closed FelixLisczyk closed 2 weeks ago

FelixLisczyk commented 2 weeks ago

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

  1. Go to an empty workspace
  2. Open Finder
  3. Open a second Finder window
  4. Close the second Finder window

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:

1034 | Finder | 
1028 | Finder | Desktop

Console output of aerospace debug-windows: debug-windows.txt

Checklist

aerospace CLI client version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201
AeroSpace.app server version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201
nikitabobko commented 2 weeks ago

Can't reporduce in macos 15.1 Beta 3 (24B5035e). The problem is somewhere on your side

FelixLisczyk commented 2 weeks ago

@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.

kennethkn commented 2 days ago

Same issue here. I'm on macOS 15.0 RC (24A335) & AeroSpace v0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201. If you repeatedly close and open a finder window, it gets a smaller tile each time, which means windows that are closed aren't getting removed from the tree. I have no other active applications that could cause this. Would appreciate any help to troubleshoot.

FelixLisczyk commented 2 days ago

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.

kennethkn commented 2 days ago

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.

FelixLisczyk commented 2 days ago

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.