14" M1P on Monterey 12.0.1 Memory Leak

[cababah]

I keep seeing this come up as "callservicesd"...anyone know what this is? It is using up 25GB of RAM! Closing all apps does not make it go away - only a restart.

The first time I saw this was after a Zoom group call and the second time was after a group FaceTime call so I assume this is related to either of these apps? Just not sure how to kill it since it persists even after they are closed 🤷‍♂️

Update - based on this post from the front page about the memory leak issues in Monterey, I think this might be the culprit:

Users Reporting 'Memory Leak' Issues After Updating to macOS Monterey

Big Sur 11.6.1 exhibits the same problem. The culprit is Facetime configured in Continuity mode to initiate / accept calls from an iPhone. In this day and age to see memory leaks in modern software is literally perplexing.

forums.macrumors.com

I disabled this for now...will report back if this process is still going haywire...

 

[cal6n]

Double click the process in Activity Monitor. A window will open with a "Quit" button.

I am having a similar issue with Control Centre. When I quit that, it respawns at a more manageable level - for a while at least.

I believe at least some of the memory leakage will be fixed in Macos 12.1 (currently in beta).

 

[white7561]

Double click the process in Activity Monitor. A window will open with a "Quit" button.

I am having a similar issue with Control Centre. When I quit that, it respawns at a more manageable level - for a while at least.

I believe at least some of the memory leakage will be fixed in OS 11.6.1

I was on 12.0 (the version that came with my MBP) while testing the hw etc for a few hours I can see control center using like 500MB or something. Definitely not normal. I upgraded to 12.1 and clean installed it before installing my apps etc and so far haven't gotten any system memory leaks!! They might have fixed it.

I usually never put beta OS on my daily driver for reasons. But it seems like for now the beta is actually more stable and contains more fixes than the original 12.0.1 on these new MBPs. When it's all stable I would prob get back to the stable build.

 

[cal6n]

I was on 12.0 (the version that came with my MBP) while testing the hw etc for a few hours I can see control center using like 500MB or something. Definitely not normal. I upgraded to 12.1 and clean installed it before installing my apps etc and so far haven't gotten any system memory leaks!! They might have fixed it.

I usually never put beta OS on my daily driver for reasons. But it seems like for now the beta is actually more stable and contains more fixes than the original 12.0.1 on these new MBPs. When it's all stable I would prob get back to the stable build.

Yeah, I meant macOS 12.1, not 11.6.1. I've amended my my post. Thanks for that.

 

[LeloR8800]

Yeah, I meant macOS 12.1, not 11.6.1. I've amended my my post. Thanks for that.

Hi cal6n,

Can you repost if you are still not getting any memory leaks in another few days, so we know it's that there is some easy fix until the problem is resolved?

 

[zarathu]

You like me and almost everyone who uses Monterey has the dreaded memory leak bug. Apple will fix it eventually.

Before then there is a simple temporary solution. Presumably you have several desktops on your mac. I have 11 at the moment. Go to one you don’t use often and open up Activity Monitor(its in your applications and on every mac). Leave it open all the time. Click on the column that tells you the use of memory by system processes and apps. Highlight(click on) any that look completely out of control, and then click on the little icon with the x in the middle of a circle. Choose force quit. If its an app it will quit and you will have to restart it. If its a process(weird names mostly) then it will quit but come back almost instantly in the small size it's supposed to be. For me about 15 minutes ago I noticed that the most common culprit, Control Center(which normally uses about 26 mb of memory) was slowly sucking more and was up to 144mb. Earlier this week I found it at 14 GB.

You can keep these little buggers from stealing memory by just keeping an eye on them. Be advised: if WindowServer is up at 1gb then its probably doing it too, and if you force quit that one, your screen will go black for about 5 seconds while the OS puts it back, and then you will have to type in your machine password again.

Hope this helps.

 

[LeloR8800]

You like me and almost everyone who uses Monterey has the dreaded memory leak bug. Apple will fix it eventually.

Before then there is a simple temporary solution. Presumably you have several desktops on your mac. I have 11 at the moment. Go to one you don’t use often and open up Activity Monitor(its in your applications and on every mac). Leave it open all the time. Click on the column that tells you the use of memory by system processes and apps. Highlight(click on) any that look completely out of control, and then click on the little icon with the x in the middle of a circle. Choose force quit. If its an app it will quit and you will have to restart it. If its a process(weird names mostly) then it will quit but come back almost instantly in the small size it's supposed to be. For me about 15 minutes ago I noticed that the most common culprit, Control Center(which normally uses about 26 mb of memory) was slowly sucking more and was up to 144mb. Earlier this week I found it at 14 GB.

You can keep these little buggers from stealing memory by just keeping an eye on them. Be advised: if WindowServer is up at 1gb then its probably doing it too, and if you force quit that one, your screen will go black for about 5 seconds while the OS puts it back, and then you will have to type in your machine password again.

Hope this helps.

Zarathu,

Did you find the memory leak still occuring on 12.1 beta?

 

[cal6n]

Hi cal6n,

Can you repost if you are still not getting any memory leaks in another few days, so we know it's that there is some easy fix until the problem is resolved?

I have been killing the process every couple of days, once it gets above 1 or 2 GB. I haven't let it blow up like it did originally, when it was reported by Activity Monitor as being around 40GB one week after I received it.

It is currently around 600MB. I will leave it running for a week, and report back next Saturday if I remember.

 

[alexqndr]

I think I have a pretty bad case over here. M1 Max with 64GB of RAM. Look at Apple Music, this is ridiculous.

Logging out seems like the least painful solution.

 

[zarathu]

Zarathu,

Did you find the memory leak still occuring on 12.1 beta?

I never upgrade a system until .4 or .5. I only ha e 12.0 because I bought a new M1Pro. I do find that after foc e quitting these apps a few times they seem to learn, and I don’t appear to have the problem anymore.

 

[Hombre53]

From "It Just Works" to "We will fix it eventually". Things in Cupertino just don't seem to be quite the same anymore, unfortunately.

 

[TinyMito]

I just hope the update comes soon, I am getting tired constant check and quit Control Center.

 

[nortonandreev]

I never upgrade a system until .4 or .5. I only ha e 12.0 because I bought a new M1Pro. I do find that after foc e quitting these apps a few times they seem to learn, and I don’t appear to have the problem anymore.

Well, it’s not like it can get any worse atm.

 

[zarathu]

I just hope the update comes soon, I am getting tired constant check and quit Control Center.

I have found that after force quitting it a number of times, CC seems to be very very slow in grabbing more memory. After a week of vigilance I don’t seem to have the issue anymore.

 

[zarathu]

From "It Just Works" to "We will fix it eventually". Things in Cupertino just don't seem to be quite the same anymore, unfortunately.

I don’t agree with you. The more complicated things become the more weird and unsualy issues creep in that can simply not be see beforehand.

 

[LeloR8800]

I never upgrade a system until .4 or .5. I only ha e 12.0 because I bought a new M1Pro. I do find that after foc e quitting these apps a few times they seem to learn, and I don’t appear to have the problem anymore.

So did the OS learned to not use as much memory? That sounds uncommon but could be comforting.

 

[FNH15]

I’m also seeing high memory usage here - unless WindowServer really does need 7+ GB of RAM?
No slowdowns, though, even when using Photoshop ’22 + multiple Excel files + InDesign ’22… Machine is amazing!

 

[macedes]

I have the same issue. Sometimes the control center is using high memory or the WindowServer.
i hope this is getting fixed in the next release.

 

[zarathu]

Zarathu,

Did you find the memory leak still occuring on 12.1 beta?

I hear that is still occurring in Beta 2 actually.

 

[zarathu]

View attachment 1907538

I’m also seeing high memory usage here - unless WindowServer really does need 7+ GB of RAM?
No slowdowns, though, even when using Photoshop ’22 + multiple Excel files + InDesign ’22… Machine is amazing!

Just force quit it in Activity Monitor. Your screen will go black for about 3-5 sec and then your login window will show up and you are back in business.

 

[zarathu]

From "It Just Works" to "We will fix it eventually". Things in Cupertino just don't seem to be quite the same anymore, unfortunately.

These systems have gotten so complicated now, and may be developed by AI’s so that no one even knows how to fix it. its beginning to look like that. When Subaru’s complicated electronic auto transmission died, no one could fix it, and a new one was just installed. This is the way of computer tech now. No one really knows how to even go about fixing this.

 

[FNH15]

These systems have gotten so complicated now, and may be developed by AI’s so that no one even knows how to fix it. its beginning to look like that. When Subaru’s complicated electronic auto transmission died, no one could fix it, and a new one was just installed. This is the way of computer tech now. No one really knows how to even go about fixing this.

You mean a CVT? Yeah, they’re not know for being reliable. Sounds like an issue on Subaru’s end.

But electronics in cars are a huge benefit for diagnostics. Diagnosis of my 2009 BMW is much easier than my ’91.

 

[5425642]

12.0.1 was teribale on my mbp 14” I did update to the 12.1 public beta

 

[cal6n]

I have been killing the process every couple of days, once it gets above 1 or 2 GB. I haven't let it blow up like it did originally, when it was reported by Activity Monitor as being around 40GB one week after I received it.

It is currently around 600MB. I will leave it running for a week, and report back next Saturday if I remember.

One week later and it's ~18GB. I've been watching it through the week, and in my case it all stems from watching videos in Safari.

I'm not seeing any memory leaks affecting any other process, and I am not seeing any "out of memory" error messages.

 

[zarathu]

I was watching a video save on my mac and when I stopped QuickTime player had boosted its nomal 30 mb or almost 800 mb.