Memory management

[jav6454]

Hello!

Quick question. As y'all know, when OS X moved from Big Sur to Monterrey, memory leakage became a thing to a point some people downgraded to Big Sur to prevent memory consumption issues.

My question is, does Ventura currently have the same memory management issues, or did Apple provide a respite of such issue?

 

[Sheepish-Lord]

Hello!

Quick question. As y'all know, when OS X moved from Big Sur to Monterrey, memory leakage became a thing to a point some people downgraded to Big Sur to prevent memory consumption issues.

My question is, does Ventura currently have the same memory management issues, or did Apple provide a respite of such issue?

Hasn’t been an issue on Monterey for awhile to my knowledge. Safari does some weird memory stuff from time to time but at think most of the huge memory leaks were ironed out such as Finder.

 

[Account25476]

Hasn’t been an issue on Monterey for awhile to my knowledge. Safari does some weird memory stuff from time to time but at think most of the huge memory leaks were ironed out such as Finder.

Too generic answer...

Please, could someone post a screenshot of its "Activity Monitor" or contribute more about the relevant issue addressed by the author? Thanks.

 

[chabig]

There is just one memory leak in Monterey, and it only affect Finder's Find command. Here is the description:

Why Monterey’s Finder Find memory leak may not be fixed

Will Monterey 12.5 fix the memory leak in the Find feature in the Finder? That looks increasingly unlikely, and may influence your decision as to whether to upgrade.

eclecticlight.co

Here is my memory graph from Activity Monitor.

 

[gilby101]

As y'all know, when OS X moved from Big Sur to Monterrey, memory leakage became a thing to a point some people downgraded to Big Sur to prevent memory consumption issues.

What memory leaks are you referring to? Most people don't have memory leak problems.

The only confirmed memory leak I am aware of is the one referenced by @chabig.

 

[5aga]

Does a beta fix supposed memory leaks that existed in prior public releases?

 

[Account25476]

There is just one memory leak in Monterey, and it only affect Finder's Find command. Here is the description:

Why Monterey’s Finder Find memory leak may not be fixed

Will Monterey 12.5 fix the memory leak in the Find feature in the Finder? That looks increasingly unlikely, and may influence your decision as to whether to upgrade.

eclecticlight.co

Here is my memory graph from Activity Monitor.

View attachment 2023485

I'm sorry but this is not sufficient because I have no information on: which apps are opened and for how long, application In execution etc..

Please, somebody provide us a screenshot of the whole "Activity Monitor" preferably of a computer that isn't shut down or restarted recently.. This is how we spot memory leaks..

 

[gilby101]

Please, somebody provide us a screenshot of the whole "Activity Monitor" preferably of a computer that isn't shut down or restarted recently.. This is how we spot memory leaks..

Sorry, that is not how to spot memory leak. Needs much more than that. A memory leak (as opposed to memory use) is shown by an unusual increase in memory use (most likely by a single process) over time with specific activity. Further, the memory is not released when activity is finished. And behaviour that is reproducible.

The Finder Find memory leak (see link above) is, as far as I know the only well attested memory leak in Monterey. The Finder Find memory leak is easily shown by following the steps in Howard Oakley's blog. You can reproduce it yourself!

 

[Account25476]

Sorry, that is not how to spot memory leak. Needs much more than that. A memory leak (as opposed to memory use) is shown by an unusual increase in memory use (most likely by a single process) over time with specific activity. Further, the memory is not released when activity is finished. And behaviour that is reproducible.

The Finder Find memory leak (see link above) is, as far as I know the only well attested memory leak in Monterey. The Finder Find memory leak is easily shown by following the steps in Howard Oakley's blog. You can reproduce it yourself!

Respectfully, I don't agree with you.

Perhaps I do not have the gift of synthesis and I have not explained myself well.

Can somebody post a screenshot of the whole activity monitor running macOS 13 please?

 

[gilby101]

Can somebody post a screenshot of the whole activity monitor running macOS 13 please?

Is this what you want. A screenshot sorted by memory for the virtual machine I am using for testing. It looks very similar to one for Monterey except for a one new process (photoanalysisd).

 

[gilby101]

There is just one memory leak in Monterey, and it only affect Finder's Find command. Here is the description:

Why Monterey’s Finder Find memory leak may not be fixed

Will Monterey 12.5 fix the memory leak in the Find feature in the Finder? That looks increasingly unlikely, and may influence your decision as to whether to upgrade.

eclecticlight.co

Have you tested this for Ventura? Seems to be better on Ventura, but I don't really have enough files in my virtual machine for a thorough test.

 

[Jimmy_Banks]

Hasn’t been an issue on Monterey for awhile to my knowledge. Safari does some weird memory stuff from time to time but at think most of the huge memory leaks were ironed out such as Finder.

Wrong.

I still have the Systemstats memory leak that starts using 10+ gb of memory randomly and doesn't correct itself until a restart. Killing the process is about a 10 minute fix.

 

[chabig]

Have you tested this for Ventura? Seems to be better on Ventura, but I don't really have enough files in my virtual machine for a thorough test.

No. I rely on Howard at EclecticLight.

Wrong.

I still have the Systemstats memory leak that starts using 10+ gb of memory randomly and doesn't correct itself until a restart. Killing the process is about a 10 minute fix.

This is on 12.4 and not using a custom cursor? I thought they fixed that.

 

[Jimmy_Banks]

No. I rely on Howard at EclecticLight.

This is on 12.4 and not using a custom cursor? I thought they fixed that.

Yep, unfortunately, 12.4 and I've never changed the cursor. M1 MacBook Pro 13"

 

[gilby101]

I still have the Systemstats memory leak that starts using 10+ gb of memory randomly and doesn't correct itself until a restart. Killing the process is about a 10 minute fix.

Though this thread is about memory leaks in Ventura, I suggest you go through various diagnostics and kext removal that I have seen suggested elsewhere for Monterey. My interpretation of posts I have seen here and Apple is that the systemstats memory consumption issue may well be related to old third-party kexts on M1 Macs. If that is so, the fix is in user configuration and not macOS. You might also want to try a clean install of Monterey.

If you wanted to test this on Ventura, I would suggest two configurations: a) your current system (or a copy exhibiting the issue) upgraded to Ventura and b) a clean install of Ventura without migrating current settings, system extensions, etc.

This is on 12.4 and not using a custom cursor?

My memory is that the custom cursor bug (now fixed in Monterey) was causing WindowServer to consume RAM.

 

[Account25476]

Is this what you want. A screenshot sorted by memory for the virtual machine I am using for testing. It looks very similar to one for Monterey except for a one new process (photoanalysisd).
View attachment 2023778

Thank you for your time.

Could you please show the activity monitor with the following columns enabled: Process name, real memory, memory, vm compressed, % cpu, cpu time, pid, threads and user please.

You're running macOS 13 right?

 

[Jimmy_Banks]

Though this thread is about memory leaks in Ventura, I suggest you go through various diagnostics and kext removal that I have seen suggested elsewhere for Monterey. My interpretation of posts I have seen here and Apple is that the systemstats memory consumption issue may well be related to old third-party kexts on M1 Macs. If that is so, the fix is in user configuration and not macOS. You might also want to try a clean install of Monterey.

If you wanted to test this on Ventura, I would suggest two configurations: a) your current system (or a copy exhibiting the issue) upgraded to Ventura and b) a clean install of Ventura without migrating current settings, system extensions, etc.

My memory is that the custom cursor bug (now fixed in Monterey) was causing WindowServer to consume RAM.

This is the first time I've heard of the kext issue, I don't see a significant amount of chatter on it while Googling either, any chance you have a thread/article in mind with some more details?

/edit/ I've done some additional reading, and this is a problem with M1? From what I read .kext extensions cannot run on M1 Macs except in safe mode?

 

[KoolAid-Drink]

Is this what you want. A screenshot sorted by memory for the virtual machine I am using for testing. It looks very similar to one for Monterey except for a one new process (photoanalysisd).
View attachment 2023778

The process photoanalysisd exists in Monterey, and I'm sure it has existed since at least Mojave or so. I believe it's for faces processing.

 

[gcortesi]

Wrong.

I still have the Systemstats memory leak that starts using 10+ gb of memory randomly and doesn't correct itself until a restart. Killing the process is about a 10 minute fix.

Agree - the systemstats memory leak is there even with 13.1. I confirm the process killing "solution" only lasts a few minutes.