AltTab showing windows that are not open anymore on macOS Sequoia dev beta (24A5331b) #3589
Comments
|
Hi, This is surprising. We usually wait until the end of macOS betas to take actions. Most bugs come and go, on Apple-side, and there is nothing to fix often after the Beta. Let's see what happens once it's out 👍 Thank you |
|
Thank you very much for your feedback. We usually observe whether there are bugs when the new version of Apple is stable.👍 |
|
Just following up on this -- the public release of macOS Sequoia is now out, and this problem persists in AltTab. After a short period of time using it, it becomes unusably clogged with windows that are no longer open. |
|
Hello, using the final macOS Sequoia this problem still persists. Expecially I have this problem with finder. Only quitting finder works to remove the windows. They cant be closed or showed through Alt Tab. |
|
Hi, |
Yes that's exactly what happens. AltTab seems to keep every window that has been open while it's running. Here is an example video. In the video I quit and restart AltTab, then confirm that only my browser (Arc) is appearing in AltTab. I then open a finder window and confirm that the finder window appears in AltTab. I then close the finder window, but it still appears in AltTab. EDIT: GitHub is terrible about video attachments, here's a link to the video: |
|
Thank you @chadlavi! The video shows the bug very clearly. It's very surprising to me because the code dealing with removing windows hasn't been touched in years. It's the essentially the same since the beginning of the project 4 years ago. Could you please try the following?
Thank you 🙇 |
|
I came looking for a resolution to the same issue - this is the output after running the suggested command: |
|
Thank you @geoffrobinson |
|
Running the command re-prompted authorization in System Settings. AltTab already had the required permissions toggled on, but I removed them, restarted the app and then re-added the required permissions.
Edit - issue persists |
|
@lwouis I see the same thing in Terminal as @geoffrobinson. This problem with permissions was happening all along with the macOS Sequoia betas. It doesn't happen when I open AltTab normally, but I get stuck when trying to actually run the binary from Terminal like this. The permission toggles are already turned on when I go to Settings, but even turning them off and on again I can't get AltTab to think it has permissions when run directly from the Terminal. Unlike Geoff, after trying to toggle the permissions I am still seeing the bug with ghost windows showing in AltTab happening. |
|
Thank you I think that when running AltTab from the Terminal, you need to give permissions to the Terminal. Could you please share the logs after the app is running and you open then close a Finder window? Thank you |
|
I ran the command on terminal -> then I opened finder on Alfred -> then closed the finder window (nothing got printed on this close action on terminal) -> then selected terminal window again. |
|
Thank you @mayur491 It is very surprising. Here's how it looks on my machine, for comparison. I've highlighted the lines about the window being closed, in bold: "Accessibility event" "AXFocusedWindowChanged" "lwouis" I find it crazy that the event It seems that people have reported similar issues on the yabai project. Here they point at Contexts as the root cause. Do you use Contexts perhaps? Thank you |
|
I don't use Contexts, but I identified AmazonQ as the cause of the problem. Once I closed AmazonQ and restarted AltTab, it started working as expected. Thanks!! |
|
Good news 🎊 I find it a bit crazy that another app can make it so AltTab doesn't receive Accessibility Events from the OS. It's clearly a macOS regression introduced with Sequoia. I hope Apple fixes that shortly. |
|
Wow, I do actually have Amazon Q. Weird and a bit concerning that it could cause this kind of problems. I just deleted Amazon Q and restarted my mac, and now I am not able to reproduce this bug. |
|
Note though that even without Amazon Q, I still can't run AltTab directly from the terminal because it doesn't think it has permissions when run that way (even though the permissions are already toggled on). |
|
@chadlavi When running the command from the terminal, you need to toggle permissions for the terminal (ex. iterm), along with AltTab. This worked for me. |
|
Please note that running AltTab from the Terminal is only to get debug logs. If the issue was from Amazon Q, and you stopped it, then you can go back to running AltTab normally. No need to run from the Terminal if there is no debugging going on 👍 |
|
oh yeah I know, just noting that running it that way for diagnostic purposes runs into a roadblock. The point about needing to give terminal permissions makes sense for this!
|
|
I've experience this as well, but I don't use Amazon Q or Contexts. As a temp fix i've just setup a script that just restarts alt tab every 3 min. It doesn't remove the issue, but it makes it less annoying as the closed windows don't stack up anymore. #!/bin/bash
while true
do
# Kill AltTab if it's running
pkill AltTab
# Wait for a second before restarting
sleep 1
# Restart AltTab
open -a "AltTab"
# Wait 60 seconds before repeating
sleep 180
done |
|
I wasn't running Amazon Q or Contexts, but Sidebar was causing my issue with AltTab. As long as Sidebar is not running, then AltTab works as designed. |
Describe the bug
When I use AltTab, windows that are no longer open appear in the window switcher
Screenshots / video
Steps to reproduce the bug
Your environment
The text was updated successfully, but these errors were encountered: