Fetching windows takes multiple seconds

[mickh]

• Version: 4.0.0 (134)
• macOS: 14.1 (23B74)

On my machine I am finding that either of the calls below takes multiple seconds to execute.

   const windows = Space.active().windows({visible: true});
   const windows = Window.all({visible: true});

Not completely certain, but this might have started happening when I updated to Sonoma. It can take up to 10 seconds for the calls to return.

A clue: the problem goes away (temporarily) if I open and immediately close a new Safari window.

Any ideas? Anyone else seeing this? Any suggestions for how I could debug further? I'm guessing that installing the phoenix source and pursuing the problem that way is the go. Or is there another way?

BTW: Thanks for phoenix. It's awesome!

[mickh]

Update: I completely quit Safari and the problem disappeared. I recently switched from using Google Chrome to Safari and, now I think about it, perhaps the problems started surfacing with that switch. Not completely certain on the timing, but I am going to switch back to Chrome for a week or two to see if the problem no longer manifests.

[kasper]

@mickh Sorry for the delay! Yes, this would indicate that one or more apps are not responding to API calls on a timely fashion, which then slows everything down. I have plans in the future to make this more dynamic and identify slowing apps faster for timeouts.

[aidan-gibson]

@mickh You aren't crazy, ever since Sonoma Phoenix has been crazy laggy for me (3+ seconds sometimes to resize a window on my normal laptop screen). To be fair my config is a disaster, but pre-Sonoma everything worked flawlessly. (also a big thank you to kasper for making this!!)

[hboon]

It's definitely Safari for me. If I kill Safari, .windows() is fast, otherwise it takes 6-17 seconds.

(.windows({ visible: true }) takes a similar amount of time)

[rcarmo]

Came here just to say that Tahoe isn't an improvement here. I can't implement anything that requires enumerating windows (like smart layouts or moving the focus to NSEW directions) without it taking 2-3 seconds, which makes it useless...

(Edit: closing Safari does "fix" it immediately, so maybe having a way to skip Safari would be a decent workaround... and thought it might be useful to drop a link to my config, which tries to cache results seven ways from Sunday...)

[LandonSchropp]

I'm pretty consistently seeing 1–3 seconds using windows. Unfortunately, Safari doesn't seem to be the culprit for me, and I'm not sure what might be. Is there any way to determine what might be the root cause?

For the others in this thread, how long does windows typically take to return its results for you when it's not slowed down?

[rcarmo]

On a laptop without Safari open, <250ms. On my desktop, sometimes with Safari closed (but other things like Remote Desktop open), 5-6 seconds.

Ironically the new Spotlight in Tahoe seems to enumerate everything including tabs in less than a second, although it populates its listing asynchronously - if I do a little creative setup like opening a Scripts folder and a page with "Scripts" in the title and type "scri", I can I see my Ghostty tab appear in the list after the Safari data even though they are ordered before Safari menus.