boppin
macrumors 65816
I have no idea what else to say about that.Same workflow in Sequoia is perfect and previous macOS releases, just not Tahoe. Clearly a Tahoe issue on Intel.
We're beating a dead horse here lol
I have no idea what else to say about that.Same workflow in Sequoia is perfect and previous macOS releases, just not Tahoe. Clearly a Tahoe issue on Intel.
We're beating a dead horse here lol
Because of you:
The process "WindowServer" takes up to 560 MB RAM, instead of up to 1.2 GB RAM before on Tahoe 26.0.2.
I try to keep an eye of it but as I said before: I noticed no really slowdown before. And as I already also said, this must be a bug in the system software because on the Intel machines I and other ones used, this happened as well. So keep cool and wait for an update.
I don't think it's a memory leak of any kind, but rather a bug in the system software. If you'd like, you can search the German-language Mac forums for the "WindowServer" process, as you'll find plenty of posts on this topic. I also rediscovered an old post of mine today where I described how the "WindowServer" process was using far too much CPU, making the system very sluggish, and I think the GUI simply stopped working.There are heavy memory leaks and it's not only about RAM utilization.
I don't think it's a memory leak of any kind, but rather a bug in the system software. If you'd like, you can search the German-language Mac forums for the "WindowServer" process, as you'll find plenty of posts on this topic. I also rediscovered an old post of mine today where I described how the "WindowServer" process was using far too much CPU, making the system very sluggish, and I think the GUI simply stopped working.
Yes. Sounds good!Well yeah there's major issues. I will check Tahoe again on another Volume in .5 or .6 to see if it's worth using on Intel. That's about 6 months or so from now.
We don’t know if the causes are relatedOkay.
Since it seems no one here has really done any research, here's something from me. There's a very interesting post in the German-language Mactechnews forum by a man named Chris. He writes that the "WindowServer" process simply crashed on his system. Hardware used: MacStudio M1 Ultra. System: macOS 26.2.
Anyway. Be that as it may. I already wrote in mid-2009, on the latest MacBook Pro available at the time, updated to Snow Leopard, that the "WindowServer" process simply crashed and left a black screen. Or in other words: this phenomenon or problem isn't all that new, but seems to be some kind of Apple tradition. I don't know. You might think so if you know the whole story and have experienced it firsthand.
WindowServer - Absturz der graphischen Benutzeroberfläche | Software | Forum | MacTechNews.de
Immer aktuelle Apple-News, Tipps, Tricks und Testberichte rund um Mac, iPhone, iPad und Co.www.mactechnews.de
Yes. Sounds good!
As I said, the problem with the "WindowServer" process and with Spotlight was observed in almost all newer versions, except perhaps on very new Macintosh models or particularly powerful machines.
Otherwise, I would suggest contacting Apple Support or, even better, submitting feedback to Apple. Ideally, this should be as detailed as possible so they can best understand the problem. Once submitted, you can only hope they actually implement the suggested solution.
And by the way some screenshots about "my" current GPU and CPU usage.
Not just Tahoe.This is one of many issues with Tahoe
As you can see.Current state of the Mac. Right now after a new start.
What is "memory pressure"? And the process "WindowServer" seems to back to normal. macOS Tahoe 26.3.
Remembers me somehow after putting 16 GB of RAM into my old 2011 MacBook Pro. No memory pressure at all. And yes, it was even visible on the first Retina MacBook Pro I owned.
I told you so! The first few newer versions, from .0 to .2, were always a bit strange, but then things settled down. That's why the advice, especially for those who earn money with their Macs, was always to wait to upgrade to version .3. I've been aware of the issues with the WindowServer and Spotlight processes since version 10.6 "Snow Leopard." It's nothing new to me.We're now at 6 days of uptime on 26.3 and I can relatively conclusively say that they did something to the memory management code that has fundamentally altered how this machine has felt through 26.2.
Or we hope that Apple will fix it by releasing.4Sorry I don't think thats the case here. 6 days was great and on the 7th we're in a spiral. Over 4gb now allocated to WindowServer for no explicable reason. I might need to reboot soon. Better than 3 days before. I think with Gurman and the others talking about how the next revision of macOS is going to be a rewrite/tighten up/clean up version as macOS has gotten so buggy you'd do well to concede a little there.
![]()
iOS 27 'Rave' Update to Clean Up Code, Could Boost Battery Life
Apple's iOS 27 update will prioritize cleaning up the operating system's internals, with engineers making changes that could result in better battery life, according to Bloomberg's Mark Gurman. The effort is said to be similar to what Apple did with its Snow Leopard Mac update years ago, and...www.macrumors.com
You’re joking. You’re comparing some random kernel panic report from an ancient operating system to whatever is going on now? Guy…Or we hope that Apple will fix it by releasing.4
Well, here's another example. iMac has 64 GB RAM but still issues. Version used 10.15.1
Panic im Standby - iMac mit 10.15.1 | Software | Forum | MacTechNews.de
Immer aktuelle Apple-News, Tipps, Tricks und Testberichte rund um Mac, iPhone, iPad und Co.www.mactechnews.de
I think we're talking past each other here. As I've said countless times before, these kinds of problems have occurred with almost every new version of macOS. Except perhaps with brand new models. But the fundamental question remains: is anything actually running slowly, or are you just admiring the Activity Monitor? I'm afraid I'm not entirely clear on that. And as for the issue of the Mac slowing down after X or X days in sleep mode, etc., that's nothing new to me either. I've experienced it not only myself, but also with people who have been using Macs since the 1980s.You’re joking. You’re comparing some random kernel panic report from an ancient operating system to whatever is going on now? Guy…
I don't even know what you're complaining about. Back then, with only 8 GB of RAM, it was probably even more.Swap now ~1.5 GB
Sorry I don't think thats the case here. 6 days was great and on the 7th we're in a spiral. Over 4gb now allocated to WindowServer for no explicable reason. I might need to reboot soon. Better than 3 days before. I think with Gurman and the others talking about how the next revision of macOS is going to be a rewrite/tighten up/clean up version as macOS has gotten so buggy you'd do well to concede a little there.
![]()
iOS 27 'Rave' Update to Clean Up Code, Could Boost Battery Life
Apple's iOS 27 update will prioritize cleaning up the operating system's internals, with engineers making changes that could result in better battery life, according to Bloomberg's Mark Gurman. The effort is said to be similar to what Apple did with its Snow Leopard Mac update years ago, and...www.macrumors.com
Nope.macOS 27 clean up makes sense, they are dumping Intel code and it will be like Snow Leopard (here's to hoping). macOS has been bloated for a while now. And no more Universal Binary, which means Apps will be smaller and the OS footprint will be smaller overall as well.
I pray. And Tsai is not optimistic. That makes me a little worried. And Gurman is basically calling them out for having ****** buggy software I think they need to actually fix it. We all use the same **** and he wont shut up about it until its fixed.macOS 27 clean up makes sense, they are dumping Intel code and it will be like Snow Leopard (here's to hoping). macOS has been bloated for a while now. And no more Universal Binary, which means Apps will be smaller and the OS footprint will be smaller overall as well.