Sidebar Sidebar
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

yitwail said:
It's a Monterey issue, but if there's another Big Sur update, maybe I should skip it in case it has the same issue.
Click to expand...
Quite frankly, that would be a bummer, if such a code regression slips through into the wild without a fix yet.
 
saudor said:
It’s in big sur at a lesser level.
Click to expand...
Even it's on a lesser level in BigSur, a memory leak is a memory leak and as it seems not bound to one-single process having a leak but multiple processes may show higher memory usage growing over time? MacOS not playing nicely with M1's UMA stuff?
 
  • Like
Reactions: JillStraw
Apple has updated my case to state that this is a known issue, and they are investigating. They do know have an external KB article yet.

The support rep did say that the more people that report it to apple, the more likely it is it will get more attention. If you haven't already, please open a ticket with Apple so they know.

Thanks!
 
  • Like
Reactions: paddylaz, Nightfury326 and gank41
Very annoying. I disabled the hide my IP from tracking. I used little snitch as well.
 
I had the Control Center issue, at one point using a whopping 60Gb! Also had the out of memory warning, and CleanMyMac was going haywire!

However, I can confirm that the 12.1 Beta (21C5039b) seems to have resolved the memory leak issue. Control Center now using a much more respectable 33Mb.

C
 
  • Like
Reactions: paddylaz
fooyork said:
I had the Control Center issue, at one point using a whopping 60Gb! Also had the out of memory warning, and CleanMyMac was going haywire!

However, I can confirm that the 12.1 Beta (21C5039b) seems to have resolved the memory leak issue. Control Center now using a much more respectable 33Mb.

C
Click to expand...
How long has it been since you installed the update?

I re-installed my OS and the problem took a couple days to come back, so I was wondering if enough time has passed for you to be sure.
 
Something crazy is going on at Apple and it has me concerned. First we find out that the M1 Macs are writing ungodly amounts of data to the SSD and now we are seeing huge memory leaks in Monterey. How could management let all this slide out into the public?

Unacceptable.
 
  • Like
Reactions: gank41
cwwilson said:
Something crazy is going on at Apple and it has me concerned. First we find out that the M1 Macs are writing ungodly amounts of data to the SSD and now we are seeing huge memory leaks in Monterey. How could management let all this slide out into the public?

Unacceptable.
Click to expand...
I was a part of that initial conversation with the huge writes to the drives on the M1 Macs, and VERY happy that was resolved. I was seeing many TBs go by and by.. I've had this memory leak issue happen to me three times this week alone, and all with the Music app. And from what I understand from everyone reporting this issue, and from my own Feedback I've filed, is that Apple isn't ready to acknowledge this as a widespread issue, even though it seems more widespread than the high SSD Writes issue. The M1 Macs are amazing pieces of hardware. The software is what's hindering them now, and this memory leak issue will eventually be fixed, just like the SSD write issue.
 
  • Like
Reactions: TheYayAreaLiving 🎗️, Gorio, baummer and 1 other person
resoverlord said:
How long has it been since you installed the update?

I re-installed my OS and the problem took a couple days to come back, so I was wondering if enough time has passed for you to be sure.
Click to expand...
I only updated overnight... so about 12 hours to date. However, still at 33Mb - so looking good so far. Will keep an eye on it.
 
  • Like
Reactions: paddylaz
ZubaZ said:
That is unless you have a bug like this memory leak and in this situation you either restart the application that is using it more than usual or restart the OS.
Click to expand...
Seems like the memory cleaner might help in this case. Is that true?
 
Running Monterey on an Intel MacBook Pro 2015 since end October and I never experienced memory leaks. I have thoroughly tested it in many situations. Are memory leaks only M1 related?
 
  • Like
Reactions: cwwilson
Mac Hammer Fan said:
Running Monterey on an Intel MacBook Pro 2015 since end October and I never experienced memory leaks. I have thoroughly tested it in many situations. Are memory leaks only M1 related?
Click to expand...
No one knoiws what set of circumstances sets it up. I can go for days without any leaks except except excessive Safari caches, and then suddenly I will notice that Control Center is sucking 200 mb of memory. Or Spotlight is now suddenly drawing 100 MB. Several weeks ago I found CC at 14.5 GB, and swap was at 190GB .
 
  • Like
Reactions: paddylaz
I also see the memory leak after many searches in finder in 12 12.01 and 12.1
Each search adds memory usage after it hits 500mb I get the loading symbol and searches take longer. This is on a. clean system. On a loaded system with 100gig of files I get 2 searches before the memory spikes and I have to wait a minute for more than 100 results to return.

I think it may be related to the 10 core chips on 16 and 14.
I have seen it on 4/5 10 core chips across the 16 and 14s.
I have not seen it on 3 different 8 core 512GB 14
 
  • Like
Reactions: JillStraw
yitwail said:
It's a Monterey issue, but if there's another Big Sur update, maybe I should skip it in case it has the same issue. 🤷‍♂️
Click to expand...
I had this problem to a lesser extent on Big Sur. It didn’t happen as often, only 2-3 times a week to the point where I had to reboot to continue working.
 
  • Like
Reactions: yitwail
Realityck said:
related

1735345 - Huge memory usage on macos Monterey in [NSCursor set]; macOS popup warning saying machine is maxed out. 70+ GBs of memory shown in warning

RESOLVED (nobody) in Core - Widget: Cocoa. Last updated 2022-06-07.
bugzilla.mozilla.org bugzilla.mozilla.org
Click to expand...
At the bottom of that page, someone claimed 5 days ago that "Apple engineering expects that the underlying issue in macOS is fixed in Monterey 12.1 Beta 3 (21C5039b), released today." That would be nice if true. 🤷‍♂️
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back