After High Sierra update WindowServer High Ram Usage

There's little to none sense in reporting bugs to Apple. At least not with theirs support center. It's a waste of time. Apple didn't do any good job with quality testing before they released High Sierra but current state of things with theirs support is even worse. You typically can get of a better quality help from open source (and free of charge) software developers/communities.

I don't think it's really so.

kernel_task always had some noticeable RAM consumption parameters according to Activity Monitor but never it had been a real issue. It's just the way it works. Unless you're seeing there numbers like tens of GBs eventually.

If Apple's QA couldn't catch WindowServer mem. leak in OS _release_ (sic!) it's a verdict to quality.

As to "If no one wants to tell" — wow, what an incredible thoughts train you're having. I _had_ reported the issue actually. I bet others did as well. So having done this and gone through hours of chats I can tell you for sure — quality of theirs "support" makes me to put quotes around that term. There's no support. There's time waste though.

> so I do not have anything against Linux.

Why would anyone care if you have anything or you don't? It's funny.

I had lost an hour with Apple's "senior advisor" who tried to persuade me that if I'm seeing this using Chrome it might be not theirs problem. They're getting paid in meanwhile. Can you imagine how big the crap there is?

I don't think it has been fixed in the release version of 10.13.1. I'm still seeing a leak on WindowServer, less rapid than before, but still there - process is up to 950Mb now after a couple of days and still growing. Reported in Apple Bug Reporter as 35015085

As per reports in other forums and my own experience this hasn't been fixed. Currently I'm on 10.13.2 Beta and end up with 20 MB RAM left when not on the default resolution. Switching to default resolution eliminates the problem. My machine is a mid 2012 Retina MacBook Pro.

I'm at 10.13.1 and have not seen the high memory usage issue with windowserver process. However, I do see high CPU for windowserver when my screen resolution on my 4k monitor is set to scaled and UI performance goes down the tube. When I switch scaled to default windowserver CPU drops dramatically and the UI performance is back.

I can confirm that setting my scaled MacBook Pro display back to 'default' fixed the problem of high RAM usage and jerky GUI interactions but I am not able to confirm that 10.13.1 fixed the problem. 10.13.1 was my initial install of High Sierra and thus my first experience with it. Hopefully a patch is out soon because EVERYTHING IS SO BIG ON MY SCREEN NOW. 😮

Yes. Firstly, the memory problem was solved in 'safe mode'. This allowed me to research the issue without the computer seizing up every few minutes. Secondly, the 10.13.2 upgrade appears to have solved the problem in regular operating mode. It has been stable for more than an hour and the memory is exactly where I would have expected it, and stable as well. Fingers crossed.

I too can confirm 10.13.2 appears to have resolved the high CPU issue I was having with WindowServer and my displays set to scaling. Now it only occasionally spikes to 20% - 30% and only briefly stays there. Nice to be able to have my 4k UHD monitor back in scaled mode.

I had high hopes when upgrading to 10.13.2 but alas.. I still have the same issue with scaled displays. The WindowServer process uses huge amounts of memory and it grows endlessly until I have to reboot. Shutting applications down doesn't seem to help much.

I think it's improved from past releases but definitely NOT fixed.

I was having problems even with scaling turned off but it cleared up on 10.13.1 after running a deep OnyX clean. FWIW I never run these kinds of utilities but downloaded and ran because nothing else was working.

Have you tried similar?

I myself don't see it as much but still do see it sometimes with macOS 10.13.2 when the Nvidia GPU is in use (some videos get pixelated or freeze when I do other things like just moving a browser window).

In an older macOS update the same thing happened and it was the Nvidia driver, not sure if it is the same thing here

That would imply there is something running when you boot normally that is triggering this effect.

Posting the EtreCheck report might give us a clue about what that might be.