Users Reporting 'Memory Leak' Issues After Updating to macOS Monterey

[bsamcash]

Base 16" M1 Pro. No issues here . . . yet.

 

[nortonandreev]

This doesn't seem to be affecting either iMac I use running Monterey. (Home and work iMacs). There must be something specific causing the problem since it only affects some users.

I have the issue on the 2021 iMac.

 

[RogueWarrior65]

Add Microsoft Outlook to this list and I'm not even running Monterey. Damn thing was hogging 3.65 gig AND IT'S JUST AN EMAIL PROGRAM!

 

[nortonandreev]

Add Microsoft Outlook to this list and I'm not even running Monterey. Damn thing was hogging 3.65 gig AND IT'S JUST AN EMAIL PROGRAM!

I mean… I wouldn’t say that’s an issue. If it was using 36, maybe yes. It’s an email program but MS Office products are quite heavy, so 3.65 doesn’t sound as bad.

 

[RogueWarrior65]

It's not just Firefox but also a whole bunch of FirefoxCP Web Content processes. Currently on my machine that's about 7 or 8 gig!! Why the hell are website such memory pigs?

 

[jgrove]

On top of this issue, I'm getting crashes in Safari 15 while using tabs normally and switching between tab groups.

Yup that bugs has been their for a while as well :-(

 

[RogueWarrior65]

I mean… I wouldn’t say that’s an issue. If it was using 36, maybe yes. It’s an email program but MS Office products are quite heavy, so 3.65 doesn’t sound as bad.

Well, given that quitting and relaunching freed up 3 gig of that, I'd say that there's a big garbage collection problem.

 

[JosephDuffy]

I've had this popup 4 times across 2 different macs today, but both are running 11.6.

Maybe it's a coincidence but it may not be Monterey only?

 

[alexe]

I really wish Apple didn't release a new major macOS version every year and focussed on stability, bug-free-ness, and long-term support instead.

 

[sunny5]

It happened to me when I used FCPX with M1 and 16GB memory. It reached 64GB memory that I have to force to quit the software many times.

 

[hovscorpion12]

Memory Leakage has been an issue since OS X.

 

[metapunk2077fail]

Didn't experience memory leaks yet. Really pushing the system.

Anyway the OS updates come fast in this time of the year.

 

[cesko]

"It's difficult to pinpoint precisely what models of Mac computers are affected.."
I'll wager it's most probably the non-bricked Macs.

 

[anticipate]

Nothing here on M1 Max 16". But who knows with bugs, they can be very complex. I had a maddening bug where my AirPods Pro and Max would cause each other to de-pair. They only fixed it with iOS 15.2 beta. Or the fact I moved one of two Macs out of the house. Who knows?

 

[laz232]

Some users who recently upgraded to macOS Monterey are experiencing a bug known as a "memory leak," a scenario in which a specific macOS process or application is bugged out and stays running for prolonged periods in the background, consuming abnormally high amounts of memory or RAM.

Now, it's been a long time since I was a SW engineer, but I've never heard of the term "bugged out" w.r.t. SW.

Also a memory leak occurs, not when an application stays running per se, but when it allocates memory, but does not release it when completed with the item, or in the case of automated systems, makes it clear that the item can undergo garbage collection.

 

[Altivec88]

I don't need ever year a new system that is buggy the first months and that gets security updates for only three years.
It would be better if Apple releases a new MacOS only once in three years but that is stable and supported for ten years.
I don't need all these bells and whistles.

Yes. Steve Jobs adamantly changed it to a yearly cycle, Its important to evolve the system yearly to keep above competitors and fresh in consumers minds. Regardless if they update every 3 years or 1 year, once they release a new system to the masses, new bugs will be found on new software.

Nobody is forcing you to upgrade. Thats all on you. I have just updated to Big Sur now at 11.6. and its rock solid. So in other words, I have yearly updates, however, I choose to update when they are solid builds. If you have the patience to wait 3 years, why not just wait 6 month for a solid build. Why are you compelled to install a .0 build and then complain about bugs.

 

[flexiboy1912]

Just checked and Control Center was using 81Gb on my 32GB MacBook Pro Max

 

[UltimateSyn]

Yeah I noticed my Control Center was using 3.5GB yesterday. Weird stuff.

 

[Kelly the Dude]

I hadn’t noticed until I read this—even through the beta. Now I see Control Center using over a gig of memory. So now it will drive me absolutely insane until it’s fixed.

 

[UltimateSyn]

Just checked and Control Center was using 81Gb on my 32GB MacBook Pro Max

Seriously??

 

[thadoggfather]

I agree. For some reason I'm reminded by the shenanigans of Federighi during the WWDC when he was showing off the beauty of Monterey.

Let's hope the bugs are squashed swiftly.View attachment 1899805

I guess best to keep that M1 Air he's fondling on Big Sur for now

 

[standing]

I guess best to keep that M1 Air he's fondling on Big Sur for now

...and that ain't no joke.

 

[macduke]

I’m usually first in line for most new Apple stuff, but not the Mac and macOS. I use that to make a living. That crap has to be rock solid. I never update before X.1, usually X.2 in late autumn/early winter. And as tempting as these new Macs have been, I’m not going to upgrade to completely redesigned hardware right out of the gate. It’s too risky.

 

[flexiboy1912]

Seriously??

Yes , I killed it and its started to grow already. I noticed last night it was 12G before I killed it and thought it was one off but seems to be slowly increasing.

My mini and 13' I updated to the latest beta last night are not seeing the same behaviour so maybe they fixed it already

Now its jumped from 1G to 2.5G already the control centre process

 

[Icewarm]

I remember when I would eagerly update to the latest OS….then it became waiting for the .1 release…..then it became waiting for the .2 release.

Apple's QA has deteriorated so badly.

maybe the yearly cadence is not a good choice