system run out of application memory

Do you have any anti-virus, "app cleaner", "optimizer", or VPN software installed on your MacBook Air? If so, please use the manufacturer's uninstaller to remove them, as they're simply not needed on a Mac, and cause more problems than they prevent. (VPNs are really only needed if connecting via secure "tunnel" to a company server).

Also, I'd look to see if you have any browser extensions installed, as one of them may be the culprit.

If nothing above helps, download/install/run the free Etrecheck app Here. Allow full disk access, and run the report. Copy the report and paste it into your reply using the Additional Text icon in the bottom reply bar. We'll be happy to examine it and see if there's something amiss.

At a glance, it appears the most crucial info needed is missing. What is your internal hard drive size and how much free space is available?

To see: System Settings-->General-->Storage

MacMikeInOK Said:

“At a glance, it appears the most crucial info needed is missing. What is your internal hard drive size and how much free space is available? To see: System Settings-->General-->Storage”

———-

RAM is the issue here —not data storage. RAM allows for multitasking. It pulls stressor the CPU, allowing things to run quicker. So, that is why to perform the restart.

dog-tired Said:

"system run out of application memory: Lately I have been receiving this message on my mac book air, system run out of application memory, force close applications. It seems to happen after updates and when my browser is trying to open.[...]"

-------

Getting that message, restart your Mac.

Glad I was able to help.

I would still strongly encourage you to uninstall your anti-virus app. If you leave it on, it's not a matter of IF you'll have an issue caused by it....it's just a matter of WHEN.

TheLittles...thanks. While I realize the difference between RAM and storage, very little available storage can result in this situation as more and more pressure is put on the RAM. (But I agree, I probably should have explained this better. And, obviously, with the amount of available storage, that wasn't the problem).

(And I have to do a better job of assuming a restart has already been attempted...all too often this simple step is overlooked...😄)