This has happened 2x now with my M1 iMac. Luckily I haven't lost any of my writing for school. Hopefully an update to resolve this issue comes soon.
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
It's fallen off a cliff and the fact Apple are integrating more Swift will produce these results.
I wonder how memory leaks actually happen in 2021.
Afaik, Swift uses automatic reference counting (ARC); so unless there‘s a bug in Clang memory leaks should be a thing of the past.
Not too sure, but I believe the same is true for Objective-C these days.
What makes me think the culprit could be one of the underlying Foundation classes, which should be C-based.
Ideas?
Last edited:
I agree that Apple is moving too quickly and not focusing on making the OS solid. Updates every two years would be a much better plane. Back in the 10.4 to 10.9 days (and certainly from System 6 to System 9), the OS was released when it was ready, not when Marketing said it should be.
Is anybody noticing this on Intel macs? I only skimmed the seven pages but it seems like everybody who was having issues mentioned an M1 device.
Control Center is using 44.3 MB of RAM right now on my 2018 Mac Mini (uptime of 10 days) and Firefox is at 1.57 GB (with 870 tabs open, most of which are suspended, so this is fairly normal usage). Nothing seems abnormal at all.
Unified memory shenanigans?
Control Center is using 44.3 MB of RAM right now on my 2018 Mac Mini (uptime of 10 days) and Firefox is at 1.57 GB (with 870 tabs open, most of which are suspended, so this is fairly normal usage). Nothing seems abnormal at all.
Unified memory shenanigans?
?
forums.macrumors.com
Huge safari memory leak
After I updated to Big Sur, Safari is having an huge memory leak on my MacBook pro 16 ! I'm The system asked me to close it because RAM was ending. (showing an unrealistic 106 GB because I have only 16 GB of RAM, but it asked me to close it!). I tried to disable extensions but nothing changed...
forums.macrumors.com
Down from 2755! I was working to close everything in time for a clean install of Monterey, but I obviously failed.
I probably should talk to somebody at some point in my life, though.
yesterday i plugged in a ssd drive with catalina into a MacBook air with 40GB of space free
after trying to log into iCloud and other log in things, the space shrank to 8GB in minutes without installing anything.
i erased the drive and installed mt lion over that, but the GB gobble was very strange
or maybe not, with apple anymore in 2021.
after trying to log into iCloud and other log in things, the space shrank to 8GB in minutes without installing anything.
i erased the drive and installed mt lion over that, but the GB gobble was very strange
or maybe not, with apple anymore in 2021.
Software is a weeeee bit more complex than that. Chances are it's not just "a bug" that they can squash and be done. Bugs can crop up in vey specific circumstances that are difficult to reproduce. It's possible that all of their tests have not triggered the bug. So, yes, more tests are needed.
When you were running the Public Beta, did you submit the feedback to Apple to help them identify the cause in your particular use case? That's what the Public Beta is for, after all.
Well, one reason to make people on Macs with 8GB RAM to upgrade sooner, I guess.
Seriously, what's the point of all the beta period if things like this keep happening? I mean is Monterey using a completely new kernel or something?
Seriously, what's the point of all the beta period if things like this keep happening? I mean is Monterey using a completely new kernel or something?
I doubt it’s difficult to reproduce if it’s been happening for 3 months, on various devices, with most stock apps and sometimes few times a day per device.
They were busy reverting back all ridiculous changes they made in Safari.
Big Sur 11.6.1 same issues particularly Safari and Apple Music.
I agree completely with your take, however the other part is this: did anybody of the thousands of people behind creating the OS noticed that Firefox, or Control Center or anything was eating away all the memory? I find this either crazy or it’s happening in rare enough instances that nobody caught it for all these testing months.
To be honest, whoever’s responsibility it might ultimately be, for us the user clients is becoming a bit too much I think.
If today’s applications are exponentially more complex, then just take the required more time for that… the biggest offenders in my opinion are those console games which take 200GB to install to soon after have a Day-0 hotfix patch of also 200GB. Give me a break, imagine if Nintendo during the NES era launched non working games? The only reason companies are getting away with it is because there’s a (luckily) failsafe mechanism in place.
That said, yes, I installed Big Sur not that long ago, I stopped hearing about bugs and issues for long enough.
Apple should go to a two year OS update schedule. Besides the stability and bug factors it will also give smaller devs a chance to develop their offerings rather than constantly have to be in new macOS mode.
Apple's new method of planned obsolescence.
1. Sell MacBooks with pre-configured 8GB of RAM, knowing most people would buy the pre-configured models.
2. Update the OS with severe memory leaks and swap SSD usage.
3. Expect some upgrades by next year from people thinking they didn't buy enough RAM.
4. Report another record breaking quarterly result.
1. Sell MacBooks with pre-configured 8GB of RAM, knowing most people would buy the pre-configured models.
2. Update the OS with severe memory leaks and swap SSD usage.
3. Expect some upgrades by next year from people thinking they didn't buy enough RAM.
4. Report another record breaking quarterly result.
Stuff like this is really hard to track down. I can't reproduce it on my work or personal machine, and none of my coworkers are seeing it on their machines. I'm wondering if specific configurations of things are causing this but I don't know.
A big problem too with betas is when people do encounter a problem, they often don't file bug reports so Apple has no way of knowing or collecting the system info they need to diagnose the problem.
There's plenty of ways to still cause a memory leak. ARC just catches the most common ones. You can still create retain cycles easily with closures and numerous other things. Also not all of the OS is built on Swift and Obj-C. There's going to be lots of C++ and C still floating around.
Bugs are understandable, but something like memory management, one would think, shouldn’t be hugely different than previous macOS versions, unless there’s a significant change under the hood. And it’s Apple that keeps bragging about them controlling both software and hardware… ? yet we have bugs aplenty.
In terms of reporting, I believe there would be reports. But even in this forum, you can read people’s annoyance with how Apple seem to ignore certain reports of bugs until many moons later. Apples lack of transparency makes things worse.
I’ve gotten these messages multiple times today running Lightroom - 16” MacBook Pro M1 Max with 32GB ram, running Mavericks. Lightroom hitting 200% CPU editing & exporting files.