I'm using a MBP 13" 2014 on macOS high Sierra with a 4k monitor.

The memory usage of WindowsServer can go quite high (up to 40 GB).

The only solution I found is to reboot my computer -- as the memory usage never goes down. The problem started with MacOS Sierra I think.

Does someone has a piece of advice or a better solution than rebooting my computer ?

enter image description here

And after closing all the running apps on my computer, it is nearly the same memory usage: enter image description here

  • Tried relaunching your browser? - that's using a colossal amount of RAM too, by the looks of it. – Tetsujin Jul 25 '18 at 9:33
  • 1
    Well, I was doing data analysis with Jupyter which explains the memory used by the browser. I just closed all my apps, I have 6.87GB of memory used by WindowServer. – Adrien Pacifico Jul 25 '18 at 9:50
  • 1
    Having the same problem on a mid-2012 MBP running 10.13 High Sierra and just using the built-in display. WindowServer was at about 6 GB of memory usage after 20 days of uptime. Closing Chrome didn't affect this noticeably; after doing so, WindowServer was responsible for more than half of the computer's total memory utilization. Logging in and out reduced WindowServer to 100MB of memory use even after reopening Chrome. – intuited Feb 7 '19 at 20:57
  • Further note: display is running at default resolution. – intuited Feb 7 '19 at 21:06

According to this article this appears to be a bug in the system when used with a Scaled Display resolution

This seems to be a bug with scaled screen resolution (specially with 4K monitors) in MacOS High Seirra (and perhaps in older versions of the OS as well). Using "Default for display" screen resolution seems to fix the issue (Not my ideal resolution, but a temporary fix until an MacOS update with a fix is available). More information here: https://www.tonymacx86.com/threads/windowserver-memory-leak-on-high-sierra.233510/

I am using a scaled (external) display and I am facing a similar problem which is what led me to this topic.

| improve this answer | |
  • Since I bought a new MBP 15" 2018, I do no longer have the issue (and I try to resell the old 2015 MBP 13'). Even though it does not solve the issue, I tick it as answered since I will not be able to check if one's answer is solving this issue. I a new answer comes up with a seemingly working solution I may change the tick. – Adrien Pacifico Apr 11 '19 at 9:11
  • 13
    Hi All, I've got the same problem with a MBA Retina 13" 2019 macOS Catalina 10.15.1. Any ideas welcomed. Thanks. – philippeko Nov 26 '19 at 15:35

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .