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

Glad I went back to Big Sur. A day with Monterey and my iMac's performance was in it's boots. Just navitaging the OS and launching apps. Back to Big Sur and zippy again. You should not need a supercomputer to run your OS. And besides the feature set isnt worth it. THis is like Catalina all over again. GOing to wait until next year I think.
 
ZipZilla said:
we know this about apple and lack of QA for OS updates. After 20 years of this, I just run a full version behind. sometimes I lose out on enjoying new features, but avoid problems like this
Click to expand...
And some versions never get fully fixed before the next version is out, so then you have to skip an entire version, and wait for the newer version to get sorted out. High Sierra wasn't great, Mojave is pretty solid, Catalina was a dumpster fire.... I don't get the feeling that either Big Sur or Monterey are winners though either, so this is a problem. I'm still on Mojave.
 
  • Like
Reactions: Nightfury326 and DVD9
On the original firmware. The Monterey that came from MBP 16. When I was testing the hw etc I noticed the control center climbing. Since I'm going to beta and clean installing it again it seems like it's fixed. So seems like the mem leaks have been fixed on 12.1 beta. Crossing my fingers it's not just luck. But an actual fix
 
How? Just how, does this pass the testing team? Do they even have a testing team anymore? No, not even that, how does this pass the development team's own tests before even making it to the testing team? There's some serious levels of incompetence going on in Apple's software department, and has been for years now. I feel like I could apply for a job at Apple, and fail to get the job, for not being incompetent enough to fit into the culture.
 
  • Like
Reactions: Mr Todhunter
white7561 said:
On the original firmware. The Monterey that came from MBP 16. When I was testing the hw etc I noticed the control center climbing. Since I'm going to beta and clean installing it again it seems like it's fixed. So seems like the mem leaks have been fixed on 12.1 beta. Crossing my fingers it's not just luck. But an actual fix
Click to expand...
This is good, I've seen both Control Center and windowserver using a lot of RAM (windowserver @ 26.4GB today).
 
  • Like
Reactions: white7561
sideshowuniqueuser said:
How? Just how, does this pass the testing team? Do they even have a testing team anymore? No, not even that, how does this pass the development team's own tests before even making it to the testing team? There's some serious levels of incompetence going on in Apple's software department, and has been for years now. I feel like I could apply for a job at Apple, and fail to get the job, for not being incompetent enough to fit into the culture.
Click to expand...
The honest answer to this is that software cycles move too fast and are never in sync. When you start doing QA, you have to lock every version of every piece of software you are testing compatibility for. But the time you actually release something, all those versions have changed and it's possible there is a breaking change. There is no real way to "fix" this other than releasing older software and extensions that are known stable because that's what was tested in QA. Server operating systems handle this by creating a software fork that does just this, often called LTS. Consumer grade software moves way too fast for this to make sense.
 
I am guess this has something to do with Swift UI and Swift? But then it also happens with Firefox as well.
 
nortonandreev said:
12.0 has the bug as well. If I was you, I would upgrade to 12.0.1.
Click to expand...
Okay, I'll probably do that. I actually just received the machine about an hour ago and no problems so far. But I'll probably do that 12.0.1 update. I'm guessing that's basically addressing security and a few drunken Friday-afternoon dev brainfarts?

Mostly, at the moment, I'm just pondering existence as I stare at LaunchPad "Installing..." Xcode 13.1... for an eternity...
 
  • Like
Reactions: nortonandreev
ralphthemagi said:
The honest answer to this is that software cycles move too fast and are never in sync. When you start doing QA, you have to lock every version of every piece of software you are testing compatibility for. But the time you actually release something, all those versions have changed and it's possible there is a breaking change. There is no real way to "fix" this other than releasing older software and extensions that are known stable because that's what was tested in QA. Server operating systems handle this by creating a software fork that does just this, often called LTS. Consumer grade software moves way too fast for this to make sense.
Click to expand...
Oh, rubbish. This is an OS level software issue, nothing to do with any other applications and their versions.
 
  • Like
Reactions: Nightfury326, Yebubbleman, deific and 2 others
Definitely not fully baked. Between this and the USB issues, my brand new m1 max is being rebooted serval times a day...and the usb issues make that a long painful process.

i wish I could downgrade, but of course, they force the new os with the new system...sigh. Haven't had one this bad in a long time.
 
sideshowuniqueuser said:
Oh, rubbish. This is an OS level software issue, nothing to do with any other applications and their versions.
Click to expand...
The OS is not a single piece of software. It is many pieces of software, with many dependencies.

The specific Control Center issue that is being reported wasn't an issue in earlier builds, but it is an issue in this build. That is most likely because someone introduced a breaking change that was able to pass unit tests and other QA tests.

Memory leaks in Mac OS aren't new. Even in earlier betas of Monterey there were memory leaks reported. Most were fixed. Some probably weren't. Others emerged as new.
 
  • Like
Reactions: Nightfury326
Monterey looks badly engineered and rushed out.

Basic stuff like printing broken (spoke to apple tech today finally, he admitted it was a known issue, with many corporate customers complaining)
 
standing said:
Let's cut people some slack. Apple's presentation of new features is so meticulously orchestrated that any person with a bit of interest in tech will get excited to experience that future now. It's not just on each person to be a disciplined human being and live by the concept of pleasure delayance.

There is a thing called mass psychology and - albeit in this case benign - Apple makes great use of it. I would argue Apple developed a habit to overpromise and underdeliver. Do I empathise with the complexity of it all, I do. But let's not pretend people are stupid for trusting a company known for quality / the so often quoted "attention to detail".

Yes, some of us, experienced in Mac OS Upgrade cycles know when to upgrade or not.

But is that the majority of people Apple is targeting with its Hollywood-like productions of product launches? How often have we heard Apple gloating over the speed and numbers of new OS adaption amongst its user base. They *want* you to have the latest OS everywhere when it comes out. It's easier for them to manage and gives them control over when people feel the "friction" to replace their device with a shiny new model.

So they do carry a responsibility. They made the stuff that breaks after a few clicks.

Again, it's not just the "naive" user who's invested into Apple's products and clicks on a button.
Let's talk about why Apple is not delivering better quality and let's focus on ideas of how we can get to a place where a gold master is not handled like a hot potato but a stable system people can and should rely on, from the moment Apple says its not in Beta anymore.
Click to expand...
Lets cut people some slack? So because "some" people are impatient and must click the update button immediately when it appears, then act as if the sky is falling because of bugs in a .0 release. Only to repeat this behaviour every year as if it's some kind of surprise. I am supposed to cut them some slack when there already is a viable solution to their problem.

These same people are saying the solution is for Apple to wait 3 years between releasees which means they are now all of sudden patient for new features (just don't put that update button in front of them). I have yet to encounter one piece of software that was bug free after a major release, no matter how long it was between updates. Windows 11 was how many years in the making. Go check and see how their initial release went off. Some bugs are only found when the masses get to use it in various different situations. Changing from a one year cycle to a three year cycle will not make things any better. The .0 version will still be buggy with the probability of it being even worse since more changes will be made during a 3 year time span.

All I'm saying is that If you don't want to deal with all the initial bugs then all you need to do is have some self patience. Wait until a .4 or .5 release. After you do this once, you can return to updating every year but instead of updating from buggy .0 to .0 you are updating from a stable .5 to .5. Problem solved.
 
Altivec88 said:
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.
Click to expand...
While I agree with you and even gave you a thumbs up, the new MacBook Pro ships with Monterey and I'm pretty sure it can't be downgraded.

While there will likely always be software bugs in a operating system I stil wonder if things shouldn't be a bit more stable since Apple are behind both the hardware and the software? But I also have to say that I don't run other platforms that extensively, so maybe things are relatively stable after all. :)
 
  • Like
Reactions: johnalan, deific and Altivec88
star-affinity said:
While I agree with you and even gave you a thumbs up, the new MacBook Pro ships with Monterey and I'm pretty sure it can't be downgraded.

While there will likely always be software bugs in a operating system I stil wonder if things shouldn't be a bit more stable since Apple are behind both the hardware and the software? But I also have to say that I don't run other platforms that extensively, so maybe things are relatively stable after all. :)
Click to expand...
Bingo. This one's as buggy as anything released in many years. if you're going to make a big splash rreleasing major new hardware, the last thing you need is buggy software detracting from it.
 
  • Like
Reactions: Nightfury326
star-affinity said:
While I agree with you and even gave you a thumbs up, the new MacBook Pro ships with Monterey and I'm pretty sure it can't be downgraded.

While there will likely always be software bugs in a operating system I stil wonder if things shouldn't be a bit more stable since Apple are behind both the hardware and the software? But I also have to say that I don't run other platforms that extensively, so maybe things are relatively stable after all. :)
Click to expand...
yes...I agree about new hardware. I hate that Apple does not allow you to downgrade to a stable release. One of the reasons we didn't order any MacBook Pro's is for this exact reason. We can't be taking a chance and messing around with .0 builds. Sometimes you have no choice because you just need a new machine. In those instances, I will cut people some slack and listen to their bitching.
 
Aside from the mentioned memory leak there are other leaks that Apple is yet to fix.

I have written an application that is dealing with 50-100 network requests per second and the memory is constantly growing (reaching 1gb per day). The first version was in Swift, so I believed it was a Swift related issue and reported it here https://bugs.swift.org/browse/SR-14194. Then I decided to rewrite my application in Rust and surprisingly had the same memory issue. Same code runs fine on Linux. There seems to be a memory leak down the network request stack. Example in Rust: https://gist.github.com/telcy/b1c3a444def65dd0f1d109b6a98db0f1 Example in Swift: https://bugs.swift.org/browse/SR-14194
 
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