Relatively slow memory leak on Sonoma

[pshufd]

My M1 Pro MacBook Pro uptime is 11 days and I ran my production stuff and the system is using up 25 GB of RAM. It uses about 18 GB of RAM under Ventura and it went up to about 20 GB after a reboot. So it looks like there's about an additional 1 GB leaking every 2 days. I'm definitely glad that I have 32 GB of RAM as I had these problems in Monterey and Ventura on launch. They were eventually fixed on Monterey and quickly fixed on Ventura. So it looks like I will need to reboot the system every 2 weeks to reclaim RAM. I'll have to do the same thing on my Mac Studio.

I can live with this. With early Monterey, I had to reboot daily which was a real nuisance. Rebooting every 2 weeks isn't enough of a nuisance to try to diagnose the problem. I'll have to do this with my Mac Studio as well.

I overall like Sonoma a lot.

 

[jchap]

How are you checking the memory usage, via Activity Monitor or via a third-party app?

When you quit all apps, how much memory is remaining? Do you have any third-party apps running in the background? How much memory is free when you first boot up Sonoma?

I’ve noticed heavy and perhaps runaway GPU memory usage on Sonoma when I connect an external display, but I haven’t noticed RAM memory leak problems yet. I will also keep an eye out for that.

(Disclaimer: I generally shut down my computers at the end of the day after using them. Whether that is the best thing to do or not, I’m not sure, but it has been a very long-standing habit for me since being a Windows user.)

 

[pshufd]

How are you checking the memory usage, via Activity Monitor or via a third-party app?

When you quit all apps, how much memory is remaining? Do you have any third-party apps running in the background? How much memory is free when you first boot up Sonoma?

I’ve noticed heavy and perhaps runaway GPU memory usage on Sonoma when I connect an external display, but I haven’t noticed RAM memory leak problems yet. I will also keep an eye out for that.

(Disclaimer: I generally shut down my computers at the end of the day after using them. Whether that is the best thing to do or not, I’m not sure, but it has been a very long-standing habit for me since being a Windows user.)

I'm using Activity Monitor to track RAM.

Bootup is 10 GB. 12 GB with Firefox. I have a fair amount of office stuff that starts up. My production stuff brings it up to 18-19 GB when running. Adding Windows virtual machine got it to about 25-26 GB. I ran my production stuff this morning and RAM usage was 25 GB without the VM. I shut it down and usage was about 18-19.

I'm used to working on enterprise systems that are up, sometimes for over a year. The main thing that triggers reboots are updates.

 

[jchap]

I'm using Activity Monitor to track RAM.

Bootup is 10 GB. 12 GB with Firefox. I have a fair amount of office stuff that starts up. My production stuff brings it up to 18-19 GB when running. Adding Windows virtual machine got it to about 25-26 GB. I ran my production stuff this morning and RAM usage was 25 GB without the VM. I shut it down and usage was about 18-19.

I'm used to working on enterprise systems that are up, sometimes for over a year. The main thing that triggers reboots are updates.

It sounds like you have a lot of memory-intensive apps running. I wonder if the persistent memory leak could be due to one of those apps being incompatible with Sonoma, or not optimized for it?

 

[pshufd]

It sounds like you have a lot of memory-intensive apps running. I wonder if the persistent memory leak could be due to one of those apps being incompatible with Sonoma, or not optimized for it?

Most of the office stuff that I run is Apple stuff. I have 2 production programs. 1 is a Windows program that runs under WINE and Rosetta 2 and the other is a native Apple Silicon Java program that you can configure to use 128 GB of RAM. These programs worked fine under Big Sur, Monterey and Ventura. It's more likely an operating system thing given that the main variable is Sonoma. It's not a big deal as I typically get systems with enough RAM to deal with issues like this. I have some 350 GB of RAM in my systems so I can move these programs to other systems if it became a big problem.

 

[aevan]

My M1 Pro MacBook Pro uptime is 11 days and I ran my production stuff and the system is using up 25 GB of RAM. It uses about 18 GB of RAM under Ventura and it went up to about 20 GB after a reboot. So it looks like there's about an additional 1 GB leaking every 2 days. I'm definitely glad that I have 32 GB of RAM as I had these problems in Monterey and Ventura on launch. They were eventually fixed on Monterey and quickly fixed on Ventura. So it looks like I will need to reboot the system every 2 weeks to reclaim RAM. I'll have to do the same thing on my Mac Studio.

I can live with this. With early Monterey, I had to reboot daily which was a real nuisance. Rebooting every 2 weeks isn't enough of a nuisance to try to diagnose the problem. I'll have to do this with my Mac Studio as well.

I overall like Sonoma a lot.

My MBP M1 Pro has 16Gb RAM and Sonoma flies on it. I do some heavy Photoshop, Zbrush and open a bunch of tabs in Arc - not the heaviest, but not the lightest of workloads. Didn’t notice the leak, though, I’ve been on Sonoma since the first PB.

 

[pshufd]

The memory leaks look to be associated with WindowServer and SiriAUSP as they are taking up 2.93 and 2.79 GB respectively. I think that WindowServer was using 300-500 MB in Ventura. I'm not sure what's up with Siri as I don't use it.

My M1 Studio has been up for 16 days so I guess that it has grown slowly over time.

I do not see any other abnormal memory use from anything else.

I have not upgraded to 14.1 yet and it's a good time to do so.

I shut down everything except for Software Update and Activity Monitor and the system is using 15.24 GB of RAM so definitely memory leaks.

 

[pshufd]

The memory leaks look to be associated with WindowServer and SiriAUSP as they are taking up 2.93 and 2.79 GB respectively. I think that WindowServer was using 300-500 MB in Ventura. I'm not sure what's up with Siri as I don't use it.

My M1 Studio has been up for 16 days so I guess that it has grown slowly over time.

I do not see any other abnormal memory use from anything else.

I have not upgraded to 14.1 yet and it's a good time to do so.

I shut down everything except for Software Update and Activity Monitor and the system is using 15.24 GB of RAM so definitely memory leaks.

SiriAUSP is 68 MB and WindowServer is 1.15 GB after 14.1 update and restart. RAM usage is 9.72 GB with only Activity Monitor running which is a bit on the high-side but maybe the On-Screen Widgets use up a lot of RAM.

 

[pshufd]

5 days of uptime on 14.1 and WindowServer is 660 MB which is reasonable given my number of virtual desktops and on-screen widgets. I do not see the SiriAUSP process in my top memory processes so these problems appear to be fixed with 14.1.

 

[pshufd]

14.1.1 has made some more improvements in this area. I installed yesterday and memory use was a little lower this morning. There was a very annoying widgets bug where they would die and a runaway process remained chewing up CPU time. I could tell this was happening because thermals went up from normal. I would have to kill the process and then the widgets would return until it happened again. This problem seems to be fixed now.

So the problems were mildly annoying but I'm hoping that this takes care of the bulk of my issues.

I have one remaining issue of Universal Control not being able to go to another system for a few minutes but that's unrelated to memory leaks.