Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
 
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.

WindowServer is not the end all be all for WindowServer module. There are heavy memory leaks and it's not only about RAM utilization.

There is also consistent GPU leaks even on idle the GPU is working. I'm never going to touch Tahoe on Intel. I'll just retire this MP in 12 months or something and get a M5 Ultra Mac Studio.
 
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.
 
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.

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.

I don't see anything I need on Tahoe that is life changing for me to move to Tahoe from Sequoia on Intel. I'll only come back on Tahoe if Apple matches the Sequoia performance by the end of it's cycle, but I doubt it.
 
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.
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.
 

Attachments

  • Bildschirmfoto 2026-02-14 um 22.38.02.png
    Bildschirmfoto 2026-02-14 um 22.38.02.png
    131.7 KB · Views: 88
  • Bildschirmfoto 2026-02-14 um 22.38.07.png
    Bildschirmfoto 2026-02-14 um 22.38.07.png
    303.1 KB · Views: 97
Okay.
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.

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

We don’t know if the causes are related
 
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.

This is one of many issues with Tahoe
 
I can't be sure yet, but so far my experience with 26.3 *seems* better memory management wise. I don't want declare it yet but we're three days in and the pressure numbers are staying inside of much more reasonable ranges it *seems*. Will keep using and report back. Wondering if anybody else is seeing the same?
 
This is one of many issues with Tahoe
Not just Tahoe.

I as wrote before it was also in every release of OSX on mostly every Intel-based Mac to see this issue. Even too much CPU usage for "WindowServer" or "Spotlight".
 
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.
 

Attachments

  • Bildschirmfoto 2026-02-16 um 22.41.28.png
    Bildschirmfoto 2026-02-16 um 22.41.28.png
    49.1 KB · Views: 100
  • Bildschirmfoto 2026-02-16 um 22.41.21.png
    Bildschirmfoto 2026-02-16 um 22.41.21.png
    59.9 KB · Views: 94
Regarding memory usage itself, I think it also has something to do with the programs being used. I remember that back then, GIMP (gimp.org) used up to 2 GB of RAM just after launching the program on an Intel-based Mac. That doesn't seem to be the case anymore. So, I would either complain to the developers of such programs or really consider switching hardware platforms.
 
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.
As you can see.

My RAM is filled up to 99.875%.

Everything runs just fine and fast. Don't see your problems at all here. Now is its up to 3.28 GB RAM compressed but nothing slowly at all here. "Memory pressure" is all green, no swap used so far and I don't know what to complain all about it.
 
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. I have not changed my workflow at all. I use all the same apps. All the same windows. Memory usage is lower, pressure is lower. Windowserver uses less memory. It feels much much more like it did on Sequoia. My guess is they are catching hell for how awful it has been not just from external users but internal too. Dogfooding is real and as macOS spins out into bug land you can believe the internal voices have gotten louder. This is a good start.
 
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.
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.
 
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.

 
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.

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

 
You’re joking. You’re comparing some random kernel panic report from an ancient operating system to whatever is going on now? Guy…
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.
 
Swap now ~1.5 GB
I don't even know what you're complaining about. Back then, with only 8 GB of RAM, it was probably even more.

Eh - later on.

In 2016

According to my activity monitor, I have 1.36 GB in swap space and 2.92 GB compressed. Nothing is running slowly here at the moment.

So I guess your CPU usage is too high.
 

Attachments

  • 512587.png
    512587.png
    16.2 KB · Views: 83
Last edited:
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.


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.
 
  • Like
Reactions: Wolf1701
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.
Nope.

Both binaries are separated from each other.
 
Honestly, guys. Somehow I get the feeling and impression that you don't just use your boxes, but rather stare reverently at the activity monitor and think you can read something special into it.
 
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.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.