Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Monterey Memory Leak

The memory leak problem still exists in 12.3.1. Is no one at Apple working on this problem? It's been months since it was first reported, and it continues to plague Monterey users. In my case, it's made Mail useless. It's time this was fixed.


JC


PS: Yes, I have cleaned up everything. Yes, I have rebooted. Yes, I have reset the PRAM. Yes, I have tried it in safe mode. Yes, I have reset the pointer prefs. Yes, I have tried turning off my mail accounts. Yes, I have reinstalled Monterey. It takes it about two minutes for Mail to use enough memory (about 120 Gb) for MacOS to automatically force quit it for lack of app memory.

iMac Line (2012 and Later)

Posted on Apr 20, 2022 12:23 PM

Reply

Similar questions

8 replies

Apr 21, 2022 12:38 PM in response to Tigerator

Workaround, until this bug is fixed: If you get this problem with Mail, as I did, rather than Firefox or other apps, then you can work around it by forcing Mail to rebuild its database.


If you use Mail in the usual way, with IMAP servers such as iCloud, Google, Microsoft, etc., then it's easy to do that:


From the Finder's desktop, choose Go -> Library to open your library folder.


  1. In that folder, rename the folder "Mail" to "MailSave", just in case. This saves the entire state of your email.
  2. Close the library folder window.
  3. Start up the Mail app. It will automatically rebuild a new Mail folder in your library, and download all of your email from the IMAP servers. (This may take some time, so leave Mail running for a while.)
  4. If (and only if) you are one of those power users who makes special email folders on your Mac, then in the Mail app, choose File -> Import Mailboxes, and navigate to Library/MailSave to find the .mbox file of the special folder and import it into your new Mail folder.


That's it. Carry on as usual. You will have to check your Preferences in Mail and re-create any rules or other customizations you may have done, but otherwise, all should be well and you should be back to normal without the memory crashes.


JC

Apr 20, 2022 8:06 PM in response to BobHarris

Yes gents, you are right, I should be reporting and assisting rather than ranting about this frustrating problem. Sorry for the unhelpful rant. Just so you know, I'm collecting and packaging a runnable snapshot to reproduce it (I've already submitted a dump and trace). From the trace, it looks a lot like the problem is a cascading sequence of page faults starting with a single one. A possible cause of this behaviour is a page fault in the page fault handler/reporter. MacOS had one of these before, some years ago, but that one was more common and easier to reproduce.


Apologies again.

JC

Monterey Memory Leak

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.