![]() On a lot of setup it happens so fast users don't even notice, but if you have 100s of windows, you should still have AltTab show nearly instantaneously, then you would see thumbnails flicker as they update To have snappiness + up-to-picture, i've made the UI show instantly, with the previous thumbnail (when AltTab was last invoked), then it asynchronously update the picture one by one. ![]() Of course that would be an issue for a snappy UX. Invoking AltTab means you're pulling 500MB of memory from the OS API. So lets say you have 100 windows at 5MB each. On a typical macbook the retina display makes it so each window screenshot is many MBs. The thing that's expensive is thumbnails. ![]() AltTab should have a very negligible (>1%) CPU/RAM/battery impact overall here. It's implemented using observers/callback APIs so it's very lightweight on resources. Regarding many windows and AltTab performance, i can share some internals: AltTab keeps a list of all open apps and windows and listens to their changes. WindowServer is used by every app and is interacting with all sorts of systems. macOS has bugs and the scenario of it crashing then bringing the user back to the login screen happens to me frequently, without using AltTab. Yeah without more data, it's hard to imagine what could have happened. Thank you for sharing with lots of details. In this instance, I just got an outright crash :( In the past, I have noticed that AltTab's performance can get a bit flakey (sluggish UI) when the number of windows in a space starts to increase quite dramatically. On a somewhat related note, this crash did occur when I had probably around 100+ windows open. If it helps, below is my Crash Reports confirming my WindowServer crashed along with some other things like Hammerspoon, which may well be the culprit (although I had no issues relaunching Hammerspoon unlike AltTab): ![]() Oct 10 14:48:17 AltTab: BUG in libdispatch client: mach_recv, monitored resource vanished before the source cancel handler was invoked Also super weird that after the crash, my attempts to restart AltTab manually kept giving me the following error: I then tried starting AltTab manually (which never worked as described in the original post).Īt this point, I'm still not 100% sure what caused the crash (whether it was AltTab or something else) but I can confirm this crash coincided with me opening AltTab and trying to switch to a different window. So unfortunately, I never got the opportunity to send a Crash Report via AltTab. As soon as I logged back in, most my apps were restarted automatically but AltTab (along with a few other apps) never got restarted. Unfortunately what happened was as soon as I triggered AltTab, MacOS crashed and pushed me out to the Login Screen (which I think is indicative that the WindowServer crashed). Unfortunately, I've restarted my machine and everything launches fine now, but I'll make a mental note of sharing a profile of the app next time this happens.Īlso are you sending the Crash report after you restart AltTab? It should prompt you if you want to sent it or not. Could you please use Activity Monitor and share here a profile of the app when it's not responding? I think it's called "spin dump" in the menu. Hard to say what's going on for you with the info you shared. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |