Windows does not have a monopoly on problematic updates. Many Internet users complain about several problems with macOS Monterey, sometimes simply annoying, sometimes more serious.
CONTROL CENTER TAKES 26 GB OF RAM?!
MacOS Monterey seems to have a nice memory leak at first. This term means that a process or an application starts to swallow much more RAM than it should need.
Users then see a message from macOS warning them that they will soon run out of RAM.
So glad I got 64GB of memory on my new Mac so I can use 26GB of it for control center… Wait… what. pic.twitter.com/inCOPaii1o
— Gregory McFadden (@GregoryMcFadden) October 28, 2021
Gregory McFadden, for example, noticed that Control Center took up 26.5 GB of RAM on his machine, four times the amount taken up by Final Cut Pro. But Control Center isn’t always the problematic application.
Sometimes it’s Firefox, or other installed applications. Given the number of posts pointing to a problem on Twitter or Reddit. It’s clear that this is a rather widespread bug that Apple will have to address quickly.
MACS CRASHING WITH THE LATEST UPDATE?
The second problem is already more worrying the Monterey update would make some Macs inoperable. Users who have upgraded would not be able to turn on their machine at all.
The problem seems to concern older generation Macs. Users of iMac, MacBook Air or old MacBook Pro seem to encounter the problem. Machines using an Apple M1, M1 Pro or M1 Max processor seem to be spared.
@Apple So, installing #macOSMonterey literally killed my 2020 16in #MacBookPro . No boot. No nothing. Dead. 18mo old… How long is it supposed to work these days? 🙁
Guys, update at your own risks…
— Freddy Mini (@freddymini) October 26, 2021
2019 #Apple #MacbookPro bricked again, second time in two years. Wow. Ports continue to stop working, not allowing charging, which bricks this. Can’t reset SMC because there’s no power going in. What else could help me determine I bought a lemon??? #applesupport @AppleSupport
— Daniel Lin (@itsDannyLin) October 27, 2021
We hope that Apple will provide a minor update very soon to solve this problem.