Dock goes to 100% cpu and system deadlocks. any cures?

99% of the time I use almost exactly two apps. Iterm2 and Chrome. (and ssh but...)

Since catalina I have had an issue where if I have multiple desktops, each with copies of iterm or chrome active, then swiping between them will eventually make Dock go to 100% cpu. Eventually the system freezes, I get logged out and I have to restore all my windows. I get around this by having Activity Monitor always running, and as soon as the system feel sluggish, if I see Dock going up through 95% and increasing, I kill it.


I have, at work, had two laptops replaced for doing this and we assumed it was a weird issue with the machines but now with the third machine doing the same, and this being a brand new Apple Silicon Macbook pro, It looks to be a problem in the software, and long standing to as I've been seeing this for over 2 years now.


This is really easy to reproduce.

Open some number of desktops.. having them spread across more than one screen helps.


Fire up chrome and have say 6 or more chrome windows spread across the desktops.

sprinkle in a few Iterm2 windows. Now start swiping back and forth between the different windows in different desktops. Within a few minutes (if the windows are active) doc should go to 100% and swiping will stop. Eventually all activity outside whatever app you are in will stop working and EVENTUALLY your session will be killed


This is obviously a longstanding bug.. how does one raise an actual Bug report with apple?


MacBook Pro 16″

Posted on Dec 24, 2023 12:50 PM

Reply

Similar questions

5 replies

Dec 26, 2023 10:48 PM in response to julianel

Thanks Barney, I have seen this without chrome in the picture but I need to use chrome for work so I don't often have it not running, (I have no choice in the matter). As a system developer myself with about 40 years in the OS and Kernel I can say pretty confidently that this behaviour is not really acceptable and is definitely a bug. All windows I am in are working fine and there is no resource shortage, It's just that dock goes out to lunch in a livelock. All services that rely on dock then, one after another, freeze up and after about a minute, something important enough to be noticed locks up and whatever service monitor Apple has in place decides to kill the session in its entirety. It should not be possible for a user to do that to the system by definition so it is a bug in dock or it's libraries, whether or not a user application has a bug that triggers it. Systems are getting so complicated though these days that maybe there is no-one in Apple that truly understands the entire system.


Chrome doesn't seem to be having any problems, it's just dock that goes weird.


I do have some snapshots of dock while going crazy now (it has happened a few times since the report) so attached them to my problem report at apple. Hopefully itmeans something to someone there.

Dec 26, 2023 10:38 PM in response to Barney-15E

Thanks Barney, I have seen this without chrome in the picture but I need to use chrome for work so I don't often have it not running, (I have no choice in the matter).


Chrome doesn't seem to be having eny problems, it's just dock that goes weird.


I do have some snapshots of dock while going crazy now (it has happened a few times since the report) so attached them to my problem report at apple. Hopefully itmeans something to someone there.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Dock goes to 100% cpu and system deadlocks. any cures?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.