Hacker News Reader

Comment by garblegarble | Hacker News Reader

The title incorrectly implies implies this is the only bad memory leak in Monterey (even though the author acknowledges it's not the only in an edit complaining about 'comment bombing').

While the pointer one may be the worst culprit, it's definitely not the only one - every few days I see Control Center using >3GB (once force-killed, it goes back down to 26MB). It's not a massive issue on my machine (I just check memory usage every day) but it gives a very bad impression that Apple haven't fixed it yet.

I'm sure is especially challenging for non-technical users who're more likely to be on a lower-memory system and run out of memory regularly

View on HN

> it gives a very bad impression that Apple haven't fixed it yet.

This suggests that it's a common or even universal problem, but are you sure that's the case? I've never seen Control Center use an inordinate amount of memory -- it may very well be a rare or unique issue.

edit: I see someone else ran into it — fair enough! Still, I think it's funny how often I see "I keep running into this bug, why haven't they fixed it!" on HN, considering how software developers should know, better than anyone, how often bugs are hard-to-reproduce edge cases.

>I think it's funny how often I see "I keep running into this bug, why haven't they fixed it!" on HN, considering how software developers should know, better than anyone, how often bugs are hard-to-reproduce edge cases.

We (software engineers) usually aren't any better than other customers despite having the same issues ourselves.

Everyone ships bugs that seem obvious in retrospect. Everyone has some small % of customers who hit a bug yet scream loudly about how terrible quality is and how stupid we are for shipping something so obvious. Everyone has had to make last-minute calls "fix or ship?", knowing that every accepted fix has a chance of introducing a new potentially worse bug. Anyone who deals with hardware understands what delaying software can mean.

If you haven't experienced these things then you just haven't operated at large scale yet.

IMHO I think it is perfectly fine. When you're the customer complain about whatever bothers you. That's valuable feedback.

> IMHO I think it is perfectly fine. When you're the customer complain about whatever bothers you. That's valuable feedback.

I mean sure, but you just said yourself how irrational it is. I think it's possible to complain without acting entitled about it.

I've seen enough people talking about it that I don't believe it is unique.

I check my activity a couple times a day, and there doesn't appear to be any correlation between use and control center randomly taking >1GB of memory. I could for instance check when all apps are closed and it's memory usage is high but then after a long day of work it's still floating around 30MB. I'm baffled at what the issue actually is but control center appears to be processing a lot more data now as all media seems to pass through it in some way.

Is the background apps closed as well? I wonder if you have a background app that are constantly using or interacting with the system that Command Center need to keep it updated? Honestly, I am just throwing out possible idea.

I recalled there was an issue with Google Play service consuming higher usage than other apps when Play is not in focus. Turns out it is apps that are using Google Play services for GCD or GSM, causing wake lock issues. The reason why they are seeing the higher usage because the Google Play services is the one that are interacting with the system and the network and it is the third party app that initiate the call which put Google Play service as scapegoat. Unfortunately, Android phone does not have a way to separate them.

I wonder if this also applies in macOS. I remember I had a issue with Windows service that are consuming a high cpu usage which is abnormal. I ran malware and antivirus scanning and come up clean. It still didn't explain why the service is so high. So I used ProcMon (Process Monitor) to keep a log of what is interacting with the service. It took me a while to filter it out because it have 100 new entries every second for that service. Found out it that third party app that are hitting the service hard, I assume the app was misbehaving and caused this. So I force closed the app and restart it, it went back to normal.

I wonder if macOS have process monitor for checking this out?

Yes I keep very few apps open on my laptop and zero are backgrounded. I suppose that's why I'm only leaking around 1GB where as some people I have seen are seeing control center take upwards of 3GB.

Control Center is also built using SwiftUI I believe. SwiftUI still has a lot of rough edges especially on Macs, I wonder if that's the issue?

Basically my suspicious as well. I did report lots of SwiftUI apps were using less memory when I started Monterey. But over a few weeks of use I see a lot of memory creep up once you left them opened. Apple Music sitting idle at 4GB memory.

I think the workaround for the Control Center leak is to turn off Airplay target mode in System Pref -> Sharing and then restart (kill) the CC process.

What is "Control Center"? I don't have such an app on my system running Monterey.

It's the menu bar icon that runs next to the dock and lets you control wifi, volume, screen, brightness, etc.

You made me check only me end, and indeed Control Center was sitting at 5.19gb.

Reply on news.ycombinator.com