M1 out of memory errors

I get these errors also, since installing Monterey on my M1 Air with 8GB RAM. Firefox is the biggest culprit, also with almost 29 GB. On my Intel iMac with Big Sur FF is only using 2,3 GB, when I use it to watch Youtube video’s and do other things at the same time. I didn’t get these errors with Big Sur, but then I didn’t look at the memory usage of FF.

Or maybe mail Your system has run out of application memory – error on Macs - 9to5Mac

M1 Max with 32GB is also seeing these. To me, it’s a bug that needed to be fixed then!

1 Like

Has to be a bug. All the programmers reading this forum are saying to themselves, “That’s one heck of a memory leak!”

Maybe something in the garbage collection routines in macOS specific to M1s.
Strange it has persisted and wasn’t fixed in Monterey though.

this thread is making me nervous about my M1 MBA arriving today …

I would characterize it as an “annoyance”, rather than a “show stopper”, if that helps.

Perhaps related to my M1 MBP crashing and rebooting when I close it. Also annoyance level, and doesn’t happen every time.

For perspective, I don’t use my laptop that much.

To ease your nerves a little: I’ve done a lot of work on an M1 Air (16GB, 512GB) over the past year and have never seen this problem. I use typically MS Office, Mail, BBEdit, Teams, Zoom, Slack, 3 browsers with maybe 50+ open tabs across multiple windows/Spaces Discord, News, iPadOS Discourse client, and a few more demanding apps from time to time. I go for at least 2 weeks between reboots.

I’m not saying that this isn’t a problem for people (it obviously is and I’m not trying to downplay that), but it doesn’t seem to be a problem for everyone.


In my case, that would mean the laptop crashes several times a day. You have to be more patient and forgiving than I am :wink:

Has to be a bug. All the programmers reading this forum are saying to themselves, “That’s one heck of a memory leak!”

It must be something like that, I haven’t had a problem with my Air since December last year, even though it only has 8GB of RAM.

1 Like

Yeah, pretty patient :slight_smile:

As I said, doesn’t happen every time, and may be associated with Bluejeans usage when I’m in the classroom. IDK

I’m also certain it has something to do with one or more of the specific apps, probably non-M1-native apps, being run on the systems that have an explosion of memory usage. Has to be, otherwise we would all be having the issue.

I think that I run only two non-native apps and, so far, have not had a problem. Also, whenever CleanMyMacX reports that one of my programs has crashed (I’m looking at you Mail), I restart my MacBook Air.

1 Like

Yeah, maybe a Rosetta bug.

Under Big Sur and Monteray apps on my Intel iMac bloat up to several gigs. Safari is usually the biggest offender, but Music also does it, as well some other apps at random. It never actually gives me an out of error message though, the swap file just swells up as well.

I wouldn’t even call it a Rosetta bug. The fact that Intel apps work as well as they do on the M1 Macs is beyond phenomenal. There simply are limits to how well any translation can work.

Edit: And now @Leeabe51 describes it happening on Intel Macs, too.

I have a M1 MBA and a 2019 27" iMac. Neither of these were having any problems until a few days ago, when both showed big signs of memory issues.

Numbers (with 2 speadsheets open): 7GB (typically 500MB with 8-10 open)
Mail: 4GB (typically 400MB)

Doing research this appears to be a Monterey issue, not a M1 issue. Several instances on the web state that this is a known issue for Apple and has been fixed on Monterey 12.1 beta. I have installed it and so far for the past few hours, no problems anymore.

1 Like

Possibly related: Users Reporting 'Memory Leak' Issues After Updating to macOS Monterey | MacRumors Forums

1 Like

A good article with some great user comments:

It just leaks… errr… works.

So glad I got 64GB of memory on my new Mac so I can use 26GB of it for control center…


I didn’t find either article helpful. They’re just saying people are having this problem, and soliciting input.

Also noting this problem (or one with the same presentation) predates Monterey.

May be more useful - I’m still on High Sierra so I’ve not tested these suggestions.