Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I can't remember ever seeing an "out of memory" message on a Mac before, so this was a bit of surprise. Minor nitpick, but it seems pretty lame to present the list of applications in alphabetical order instead of putting the worst one at the top...

Screen Shot 2021-10-24 at 6.03.54 PM.png
 
Has Apple software QA truly become abysmal over the last few years or have social media, blogs, and videos just made it easier to surface problems? For example, would the current Apple have released Copland?

Or maybe Zuckerberg Commandment™ #3, Keep Shipping, has somehow made its way into Apple.

Well, no matter the reason...:mad:

Honestly I think a big reason you're seeing this crap as of late is two fold.

1. Businessy types, not developers, are driving the software development and they want a "new every year" for business reasons and

2. Leet code interviews. These are interviews that favor kids out of college verses people who have written software the past 10+ years because instead of asking the important questions experienced devs should know, they ask tricky puzzle type questions kids out of college would know and that experienced devs haven't touched since college.
 
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.

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

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.
It gets a bit more complicated than that. We try to keep our systems reasonably up to date due to security issues. At the same time, our most sensitive systems need to be very behind on updates. The software our bank gave us to process checks and credit cards tends not to be very up to date. When you update the OS, the software crashes. The solution is, only use these computers for credit cards and checks. That and be ready for bad things to happen. (We keep these two computers on a separate network, yet they continue to make my hair fall out.)
 
Just curious; are machines actually grinding to a halt (which would be a symptom of running out of memory), or is it just an alert? The latter is annoying, and shouldn't be happening, but not a huge problem.
 
I guess the OS displaying dialog saying the device has run out of memory is quite an issue on its own. A normal user should never see such a popup with normal usage, yet they do atm.
I agree. But there is still some range between "annoying nuisance" and "frequently crashing PoS". This may be anything in between.
 
I only installed Monterey on my 2020 Intel MBP after reading about some dongles not working with it.
No issues so far. Apart from it seeming to run hotter than under Big Sur.
I’m now tempted to revert to Big Sur, though…
 
The main ones that I see that seem out of the ordinary, are universalaccessssd and control center.
 
It gets a bit more complicated than that. We try to keep our systems reasonably up to date due to security issues. At the same time, our most sensitive systems need to be very behind on updates. The software our bank gave us to process checks and credit cards tends not to be very up to date. When you update the OS, the software crashes. The solution is, only use these computers for credit cards and checks. That and be ready for bad things to happen. (We keep these two computers on a separate network, yet they continue to make my hair fall out.)
No one disputes developing stable software is anything but complicated.
It's not only complicated it can get very complex very fast.

But the narrative of the "naive user" is getting old.
Apple should work on stable and sustainable solutions that work independently. A core dedicated to security updates, independent of os upgrades.

As a matter of fact I'm not even sure that that's even the case. I don't know your situation in detail. But if it were as you say, I would want Apple to implement a secure framework within Mac OS that allows critical areas of legacy software to continue to run smoothly and safely.

But one has to assume they just don't want to be bothered with another layer of complexity. And it's just not a feature that works to wow people waiting for the next cool thing.

It's a pity we have to even argue about who's fault it is if a system designed by Apple is crashing after an upgrade. I'm hearing people saying "but what about third party software". It still runs on Mac OS. Apple's domain. Apple's responsibility.
 
I noticed it during the betas. Someone here told me it was related to changing the color of the mouse in the Accessibility settings.
I did have it enabled just for fun, but now I removed the option and it seems to have stopped the leakage.
 
Last edited:
No one disputes developing stable software is anything but complicated.
It's not only complicated it can get very complex very fast.

But the narrative of the "naive user" is getting old.
Apple should work on stable and sustainable solutions that work independently. A core dedicated to security updates, independent of os upgrades.

As a matter of fact I'm not even sure that that's even the case. I don't know your situation in detail. But if it were as you say, I would want Apple to implement a secure framework within Mac OS that allows critical areas of legacy software to continue to run smoothly and safely.

But one has to assume they just don't want to be bothered with another layer of complexity. And it's just not a feature that works to wow people waiting for the next cool thing.

It's a pity we have to even argue about who's fault it is if a system designed by Apple is crashing after an upgrade. I'm hearing people saying "but what about third party software". It still runs on Mac OS. Apple's domain. Apple's responsibility.
I am seriously thinking about running those apps in a virtualized sandbox. The problem with adding another layer is, you are adding another layer that might have an exploit. When it comes to security, keep it simple.
 
I am seriously thinking about running those apps in a virtualized sandbox. The problem with adding another layer is, you are adding another layer that might have an exploit. When it comes to security, keep it simple.
True. Sandboxing is not a permanent solution either.
 
Folks, I just got off the phone with an Apple Senior Advisor. They assured me that this is not an issue because they have never heard of this issue before. They also assured me that whenever an issue occurs, Apple is aware of the issue before any customer is, because Apple talks to millions of customers a minute, and quickly knows when customers are experiencing issues. So, this is the troubleshooting for this issue. First, you will need to complete a full erase and re-install of the RAM. If that does not resolve the issue, you will need to run a data capture, with Mail Logging enabled just be be safe. You'll need to replicate the issue while the data capture is running. Once it is complete, you'll upload the report. Engineering will respond within 48 hours. Because this is a known issue, Engineering has confirmed that they are aware of the issue and are investigating. They have stated Apple's Official Position on the Matter is to keep your software and RAM up-to-date with the latest versions of all software.
 
I ran into this problem last week, two days into an M1 Pro MacBook Pro with 16 gigs of ram. Apparently my music app was using 111 gb of memory… Control Center is also consuming a lot of memory. Glad to see it's a software issue, I guess…?

ETA: I did troubleshoot the Music crash with a tech since the machine is brand new. Couldn't recreate the problem but hopefully the almighty Apple Engineers can come up with a fix that we're gonna love.
 
Just curious; are machines actually grinding to a halt (which would be a symptom of running out of memory), or is it just an alert? The latter is annoying, and shouldn't be happening, but not a huge problem.
Mine actually stalled. The music kept playing, but I couldn't do anything until I force closed that specific application.
 
I reported it twice during the beta period. Maps used 90gb and growing when I noticed it. Then it happened with safari.

But they were too busy with the super useful SharePlay so I can watch a movie with my friend over FaceTime.

They keep adding rubbish instead of going back to the basics and trying to get macOS back to a stable OS.


It infuriates me so much.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.