I’ve run Clean My Mac X multiple times to clear caches, free up RAM, etc with no change. Some non-Apple but very widely used apps take a minute to start up. Even simply changing active windows on the desktop takes 5-10 seconds! This machine is awful. My older machine was WAY faster and more responsive. Not high expectations as I have read tons of post on internet and none of them worked by now.īrand new MBP M1 Pro 16" very slow I recently sold my 2019 MBP 15” and purchased the 2021 MBP M1 Pro 16”. It runs Monterey (12.5.1) 16 GB RAM, 1 TB SSD. The new machine is very sluggish. It takes 5-10 seconds to start any app - including native Apple apps. The computer is clean and BigSur is just installed, so any idea is welcome and I can test anything without risks. Is there any way to fix this? Or BigSur consumes so much CPU in this kind of MBP? and I am forced to go back to Catalina again?. It seems the operating system is not the problem (or it is a specific problem with this hardware). I know this is not normal as I have a MacMini 2015 (i7, 3,0Ghz, 16GB) running BigSur without problems using less than a 1% from a fresh boot. WindowServer always on top with 66% of CPU going to 80%, even more sometimes.Īnd Kernel_task always there too with 5% of CPU going to 15%, 30%. Now, the same computer running BigSur, same clean boot, just after a fresh installation from a bootable USB of BigSur 11.3. None app running, just the activity monitor. Here a screenshot of the same computer running Catalina from a clean boot: Mi MacBookPro13,1 (2016, i7 2,4Ghz, 16GB ram) runs slow and it get completely unusable when I need to do normal task (mainly with Microsoft suite: PowerPoint, Teams, OneDrive and Outlook). To give it the latest opportunity I request for help to this forum to try anything to get BigSur running normal. I expected the latest BigSur 11.3 will solve the high CPU consumption, but it is not. I downgraded three times from BigSur to Catalina and it seems that I am going to do it again. WindowServer and Kernel_task always on top. This issue is also specific to 12.0.1 as this was not a problem on Big Sur or the developer beta versions of Monterey.Īny suggestions on how to prevent RunningBoardd from slowing me down every hour aside from my current solution of leaving Activity Monitor open and just having to force close it when it starts to slow? Is there anyone else having this issue? I haven't been able to find any examples of this happening to others on this hardware and software combination.īigSur high CPU use. The problem is that RunningBoardd is a system utility that pretty much monitors and manages all of the running apps in recent versions of macOS and it can't be turned off. Of course, the utility restarts itself in the background and I repeat the process an hour later. I can force close it and everything instantly goes back to normal and running smoothly. I can start to notice the system slowing down when RunningBoard gets over 85%. Everything operates correctly, more or less, but after using my normal set of work applications for an hour or so (Chrome, Slack, VPN, WhatsApp) my system grinds to a halt and all of the windows start to hang.Įach time this happens I check Activity Monitor and RunningBoardd has the CPU running at ~102%. Again, I did not have this problem before.Īny thoughts or suggestions are appreciated.ġ00%+ High CPU Usage from Runningboardd on macOS 12.0.1 I recently installed Monterey 12.0.1 after holing out from Big Sur for a little while. Still have the same problem, so it appears to be tied to the 13.3.1 release itself. I also put on the quick fix security patch, but thinking that was the problem, I backed it off. This only just started when I put on the 13.3.1 update. My "state of the art" machine is pretty much a $4,000 boat anchor. Why do I need WindowServer AND WindowManager? Why is WIndowManager eating up all my CPU resources for the simplest things? How can I fix this? I've tried to quit and force quit the WindowManager but it won't quit. I also have the WindowServer task running. And it's appears to be because of this stupid WindowManager task. Every time I open a new window or app, it takes WAY longer (10-plus seconds) to load and become active than before I did the 13.3.1 upgrade. Every time I move a window on the screen WindowManager comes to the top of the Activity Monitor list at 20-50% utilization. Every time I come out of screen saver WindowManager task goes to 100%-plus CPU utilization and hangs my system for 20-30 seconds.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |