Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Interesting. I am a developer for about +30 years from the classic mas OS 9 up to the latest macOS26 and I my experience macOS26 has very little issues with memory leaks. In fact, the last couple macOS versions are insanely good in detecting unreleased memory addresses. Even for badly writing apps, it covers those leaks not directly related to macOS itself. It's even hard to code an app with Swift that does leak memory.

So, unless you just shouting, it would be awesome if you can share some recordings with Instruments/Leaks profiles so we can take a look at it.
So often a poster has an issue and instantly believes everyone else is having the same issue when in fact is is specific to something unusual the user is doing. I see this all the time. Thank you for your rebuttal.
 
So often a poster has an issue and instantly believes everyone else is having the same issue when in fact is is specific to something unusual the user is doing. I see this all the time. Thank you for your rebuttal.
Not sure what you try say here. But a memory leak is ... well .. a memory leak and it is detectable with Instruments/Leaks. It doesn't matter what is causing it. Claiming that macOS26 has a lot of memory leak issues, is easy to shout out. But some proof would be great, not?
Mostly people who say 'it has memory leaks' doesn't even know what a memory leak is. Nuff said ..
 
  • Like
Reactions: Non-Euclidean
Interesting. I am a developer for about +30 years from the classic mas OS 9 up to the latest macOS26 and I my experience macOS26 has very little issues with memory leaks. In fact, the last couple macOS versions are insanely good in detecting unreleased memory addresses. Even for badly writing apps, it covers those leaks not directly related to macOS itself. It's even hard to code an app with Swift that does leak memory.

So, unless you just shouting, it would be awesome if you can share some recordings with Instruments/Leaks profiles so we can take a look at it.
ControlCenter since its inception is the worst offender, for an app that is basically useless.
WindowServer and Xcode memory situation is hopeless, but that they can't fix ControlCenter memory leaks is funny.
 
ControlCenter since its inception is the worst offender, for an app that is basically useless.
WindowServer and Xcode memory situation is hopeless, but that they can't fix ControlCenter memory leaks is funny.
OK, I don't want to reboot in Recovery Mode, disable the System Integrity Protection and try and trace those applications.

The reason I was asking is because I typically run the Mac all day from morning to late evening, often leaving many applications open at the same time and I haven't come close to a situation where memory was running short.
 
OK, I don't want to reboot in Recovery Mode, disable the System Integrity Protection and try and trace those applications.

The reason I was asking is because I typically run the Mac all day from morning to late evening, often leaving many applications open at the same time and I haven't come close to a situation where memory was running short.
There is almost no situation of memory running short because it will be just swapped, when Xcode starts taking 12/32gb of memory that's when I start feeling that system is feeling sluggish. As for ControlCenter, when I wrote the previous post (clean boot), it was taking 45mb now it's taking 110mb, few days later it will take 0.5gb, that's when I usually kill it.
 
RC2 Killed my M1 had to roll back, no wifi, apps hanging... I'm avoiding this balls up until is actually released!

This is the first time my mac has not liked a beta build to be fair.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.