I am even still at Mojave. I don‘t need any of the fancy features for my work, plus I can continue to use 32-bit applications.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Users Reporting 'Memory Leak' Issues After Updating to macOS Monterey
- Thread starter MacRumors
- Start date
- Sort by reaction score
Disabling this in 'Accessibility' solved the issue.
Or you can simply wait a year or two before you update, and people who want bells and whistles can test them for you.
Monterey is a .01 release currently. Need that number to go higher before I install.
Attachments
Late 2015 with 24gb ram and 1TB Fusion drive.
The machine is all but unusable since the upgrade. I can use a browser and any cloud services, but forget any applications like Excel or Photoshop. This is the worse update I have ever gone through. I converted to using 100% macs in my business in 2000 so I have seen a lot of updates but none are as terrible as this.
The machine is all but unusable since the upgrade. I can use a browser and any cloud services, but forget any applications like Excel or Photoshop. This is the worse update I have ever gone through. I converted to using 100% macs in my business in 2000 so I have seen a lot of updates but none are as terrible as this.
Same here. Mojave + MBP 2015 = never change a winning team!
Well seriously, I will have to move on when buying the new MBP, but I would really prefer Apple going for a 2-year cycle. It's totally unnecessary to press a major OS release every year. The same goes for iOS. Why not trying a flip-flop principle? MacOS 2022 -> iOS 2023 -> MacOS 2024 -> etc.
More time for Apple and the developers to make it rock stable. Serato DJ issues a warning every year now not to update immediately, and that's just one example. On the same time, the last major improvement feature for all users was, lets be honest, dark mode. Most of the rest seems like iMessage and memoji kindergarten (and barely anyone in Europe cares about iMessage or Facetime). The GUI also looks awkward since Bug Sur. Finder windows are much harder to read. But yeah...
Last edited:
Strange, on mine all went back to normal.
Biggest memory clogger is Firefox @1.1GB, yesterday it was at 40 or 50.
Running latest Monterey beta on a Mini M1.
First off. I never called anyone stupid, nor did I tell them not to update. All I said is, if its important for that person to have a stable release, they shouldn't be updating to a .0 release. It has nothing to do with being stupid or smart, its about understanding your own circumstance and knowing how major bugs will affect you or your work. I even update one of my non-critical home computers on day 1. When I was younger I would have jumped on the public betas too. The difference is I am not surprised and not up in arms about bugs because I am expecting them to be there. Your expectation of a .0 release being bug free it not realistic nor obtainable from any company, so banging your head on the wall year after year and saying bugs shouldn't be there will just result in a sore head . My second point was solely to explain, that stretching the updates to three years instead of one will not solve the problem and may make it even worse. I am not sure why any of my points are contentious or rub you the wrong way. All I did was offer a solution to those that don't want to deal with bugs or require stable machines.
I love this feature, but disabling it if it helps. So far no dice though. Has anyone tried killing the process? Does it restart itself? I don't really want to try with all my workflow open.
Update: Control Center usage hasn't got up (or down) any since making this tweak but I guess what is leaked is leaked at this point.
Update 2: After receiving a couple phone calls the usage has jumped up more. Others were suggesting it had something to do with Continuity/Hand off... maybe some truth to that?
Last edited:
I doubt this is a critical but if you were able to get around it. Annoying and should be addressed yes but hardly critical if its not taking down computers or showing privacy info. I also hope you sent off a bug report to Apple when you noticed this issue since August.
It’s critical enough for me. It slows down the computer and requires force quitting apps. For normal users, it means force restarting their computers (as not everybody knows how to use the Activity Monitor) and can also lead to data loss.
Again it should be resolved. Critical for you is not a reason to call it critical for everyone. ”For normal users, it means force restarting their computers.” I think for normal users they will try force quitting apps from the Apple menu or even option + command + escape. I think for very computer illiterate people they might try force restarting their computers. So yeah data loss is possible and has likely happened in both scenarios which is not good. I personally think you’re exaggerating how ‘critical‘ this is by your own personal experience and have lost scope of how important it actually is.
I am more likely to believe this is the minority. A critical issue would be an OS that quits/crashes on its own and destroys data on the regular. Many of the people who have posted to social media were able to quit apps and shutdown normally without data loss and the leak would come back. So yeah definitely fix it because it does affect people.
Also did you file the bug when you noticed it in August?
Memory leak of this magnitude is a critical issue for everybody.
I called apple support; they said they were unaware of any widespread issue.
They had me create a new user to see if that fixed the issue (it did not).
They then had me re-install the OS. So far not seeing the issue recur, but it's only been a few hours.
If that doesn't fix it, the support representative said they would escalate to engineering. She also said if enough people escalate to engineering, they would acknowledge it as a widespread issue and post a message; therefore, I'd encourage you all to reach out to apple support as well.
They had me create a new user to see if that fixed the issue (it did not).
They then had me re-install the OS. So far not seeing the issue recur, but it's only been a few hours.
If that doesn't fix it, the support representative said they would escalate to engineering. She also said if enough people escalate to engineering, they would acknowledge it as a widespread issue and post a message; therefore, I'd encourage you all to reach out to apple support as well.
Those are the best pr0n sites on the web.
OK, so the hardware is awesome again.... now let's make the OS awesome.
Bullsh*t
It ain't gonna fix anything, it happens on brand-new M1 MacBook Pros.