Process universalaccesssd using 8GB+ when i decided to color the mouse cursor. Back to normal BW default cursor and reboot: no issues whatsoever in the memory department, apart from having 6GB RAM free and system insisting in using ~200MB of swapping ?
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
Same. I've never seen this popup in over 15 years. I suddenly regretted having bought just an 8GB M1 iMac.
But disabling the custom mouse color in the Accessibility settings stopped this popup from appearing, and now my memory indicator is more often than not in the green.
Man, sometimes Outlook would take like 60GB.
For the record, here's apps that are typically open in my usual workflow :
Finder - Safari - Calendar - Notes - Word - Excel or PowerPoint - Outlook - Teams - Remote Desktop - Activity Monitor
Sometimes FCPX.
Not seeing anything extreme as in the article but I've gone from 12-15GB normally free (out of 32) on an Intel 16 to 8-9, with the same usage patterns. Everything seems just a little higher.
Was it OS9 (and before) where you set app-specific RAM sandboxes?
Not saying that's where we need to go, but there might need to be some type of governor to limit poorly coded apps from bringing the whole system down.
Not saying that's where we need to go, but there might need to be some type of governor to limit poorly coded apps from bringing the whole system down.
Jeez... that's brutal... they better fix this quick.
My 2021 MBP just shipped, so it's running 12.0... I'll keep an eye on it. If it's fine, I'll probably won't update for now.
I'm still on Big Sur. I've had Firefox and News (News!) crash OOM. News takes a while to get there, but I absolutely cannot leave it running. Firefox's memory leak is intermittent. I think it might have to do with the fact that I have a zillion tabs open. I've just taken to preemptively shutting it down now and then. I've just got a 16GB M1 Mac Mini, though.
I have two Apple Silicon computers and still haven't experienced this bug. I wonder what causes it. Some said that it could be the Mail.app but I doubt it.
It's sort of topsy-turvy now. Windows-haters use issues from old, obsolete versions of Windows to convey how terrible Windows is today (which Windows 10 is one of the best and most stable). Apple is the opposite. The old versions of macOS were stable and fast, and lately they are full of bugs and issues, but people still live off the myth that macOS "just works". Windows gets better, macOS is, well...not.
Last edited:
I didn’t actually realize you could change the cursor color. Now I want to try it but I guess I can’t because apparently it triggers this show-stopping memory bug. Oh well!
I'm interested in seeing if my issues are related to this. I keep getting the beach ball of doom on a base 14" M1P MBP. Only have a handful of items open. Zoom, Slack, Discord, Safari with like 10-15 tabs. Nothing too insane, my 13" M1 MBP handled this workload just fine. I did notice I was swapping memory the other day, but by the time I could get Activity Monitor fully open, it "resolved" itself.
Attachments
But, but, those 15 year old teens can’t use shiniest best emoji to flex how new they are and how cool they have become in their discord chat! /s
If music app is exclusively written on swift, I’d say it’s performance isn’t great. Scrolling with artwork displayed takes quite a while regardless and causes GB of write on SSD in a few seconds.
I was actually seeing this come up with the latest update on BigSur, suddenly seeing this same pop up dialog about low memory.
But teenagers would not be able to flex with their friends how new and how cool they are to send best emojis using a 16” maxed out MacBook Pro. /s
Someone says this every thread, with every point release, and has for the last 20 years. I didn't really use a Mac back in the OS 9 days… so I guess maybe back then things were better, but I can't comment on that.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...
Apple's software QA has never been good. I'm not sure what weird nostalgia glasses some people wear that cause them to see "flawless" upgrades that happened in the past. The conventional wisdom has always been wait for the first point release. Or, if you must have the new version on Day 1, make sure you have a Time Machine backup and be ready to do a clean install. And before Time Machine everyone used CCC (Carbon Copy Cloner).
In the early days of OS X there were so many driver or app conflicts that you might have had—which there was no easy way to check for other than reading the forums—which would cause a failure to boot after upgrade that upgrading on Day 1 felt like a 50/50 gamble of having to spend the rest of the day doing a clean install and moving everything over manually.
Last edited: