Steve Troughton-Smith says...
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
Steve knows what he’s talking about.
There are multiple different leaks that presumably have nothing to do with each other and therefore aren't resolved by one fix.
Multiple memory leak issues were fixed in 12.1 (but apparently not all).
yep, that pretty much sounds like a memory leak. I'm mostly running adobe (LrC, Ps) which isn't famous for memory handling, even though it peaks here and there, it also goes down.
Suddenly, let's rewrite it in Rust doesn't sound like a joke anymore.
I just read this story and I'll like to remind everyone contacting Apple Support is not to mention CleanMyMac X in any capacity. This is an immediate turn off as it's my firm belief that Apple sees their OS as self-maintaining and using third-party cleaners that also has a poor reputation is a no-go.
Just like it was best not to mention that you had the Application Enhancer Framework installed back in the Mac OS X Tiger days if you were to get any help - of course not via Twitter back then, but in "Genius Bars"
Just like it was best not to mention that you had the Application Enhancer Framework installed back in the Mac OS X Tiger days if you were to get any help - of course not via Twitter back then, but in "Genius Bars"
Thing is, Mac OS is *not* self-cleaning. Applications leave tons of stuff behind. It’s been an issue since day one and they should do something smart about it, like having app makers include a list of their Library files in the app package so they can be removed when the application is removed
FWIW, I was still having problems with the latest version of Outlook chewing up memory on Monterey 12.3.1. Just got an "Out of Application Memory" error -- even though I have a full TERABYTE of available hard disk space!
Sorry to hear that but you're confusing memory and storage. If you click the Apple logo in menubar and then About This Mac, you'll probably see something like Memory 8GB or 16GB. So doesn't much matter that you have a terabyte of storage.
Inactive RAM is there to be used at a moment notice if required. Your memory pressure is very low and not much swapping going on. It's working correctly.
These vulnerabilities are addressed in software. But you will largely avoid these vulnerabilities by moving to Apple Silicon.Personal data hemorrhaged into memory leak. Memory leak then read and uploaded.
Meltdown and Spectre – The Intel Kernel Memory Leak - Pegasus Technologies
The discovery is becoming more and more publicized every day, and at Pegasus, we’re actively monitoring and responding to keep our clients safe. Essentially, massive security holes have been found in Intel CPU chips, affecting the operating systems of PCs, Macs, and other devices with Intel...pegasustechnologies.com
Heck that's the truth, no /s required. Same thing with PCs since the RAM amounts grew. At least when it was lower, they were forced to code efficiently
Yes! And it's every one I've tried, Why is it already 500MB with just about:blank open?! And only a few actual websites open, it's pushing 2GB!
It's every single event that has happened since the first dinosaurHoly Memory Leaked:
WTF Calendar?
Inactive RAM does not even get a mention in Monterey Activity Monitor so you may be drawing the wrong conclusions.
There are many many reasons why the system can slow down. For example, in a previous OS, Affinity apps would take an absolute age to fire up for the first time, and that's nothing to do with memory. You might be barking up the wrong tree.
This is not intended as a tutorial of memory management in modern operating systems. Just enough to point the reader in the right direction.
"Inactive RAM" is perhaps not the best title. Every modern OS (including MacOS) uses the nearly the same virtual memory / real memory management principles.
Let's assume the computer was just rebooted. The real memory is not constrained; not under pressure using MacOS terms.
When an application (let's use MS Word) starts, MacOS will create a process (also known as virtual address space) and begin to allocate pages in real memory which contain code and data.
When MS Word is closed, MacOS will mark most of the pages in real memory as Inactive. If MS Word is open again, almost all pages still reside in real memory and the application will open very quickly. That's the real purpose of Inactive RAM. Think of it as a general purpose cache managed by MacOS.
Free RAM (real memory to be precise) is wasted memory. So Inactive RAM is "good for you".
Growth of Inactive RAM is not a memory leak, although a rare bug could exist if MacOS cannot invalidate Inactive pages and make them available for new processes. This would be a VERY rare bug.
When real memory is constrained, MacOS - just like other modern operating systems - will perform additional activities.
One of the first steps: find new pages in real memory.
- Invalidate pages in Inactive RAM (since it's just a cache)
- Examine pages in every active process and look for pages not recently referenced; mark these pages as Eligible for Page Out. This is also known as Working Set Size Trim. These pages in real memory will be paged out (or swapped) to the swap file and become available again
Memory leak is a completely different problem. In short - memory leak is created when program logic continues to allocate new pages and retains pointers to these pages. The operating system cannot invalidate these pages because they are a part of the address space while not being referenced. The end result is a misleading message that the system is out memory.
In practice, this is what happens during a memory leak. Let's create a string and add a new character continuously: "leak+leak+leak" ...
- New pages are being created and paged-in
- Since the string is not referenced, OS marks these pages as Eligible for Page Out (trimmed)
- Eventually, these pages are need by other active applications and paged-out (swapped): moved to the swap file
- When the swap file is full, the dreaded "System out of memory" message is displayed