Need more tester, here. Found the issue and it can be reproduce. https://forums.macrumors.com/thread...ey.2321357/page-2?post=30638815#post-30638815
If you don’t want to click, that link says that the cause of the memory leak is changing the mouse pointer to a size or color that’s different from the Mac OS defaultSaw this article today. Problem solved?
https://www.msn.com/en-us/news/tech...oblem-and-the-cause-has-been-found/ar-AAQJPzW
Considering I’ve never made changes to my cursor, and I’m still having memory leak issues with the Music app, I’m saying it’s got nothing to do with it.If you don’t want to click, that link says that the cause of the memory leak is changing the mouse pointer to a size or color that’s different from the Mac OS default
Can anyone confirm that restoring it to default fixes the memory leak? And is anyone experiencing the leak without having a non-default cursor?
One thing that apparently does cause it is adjusting brightness manually or automatically while watching HDR Youtube videos.Considering I’ve never made changes to my cursor, and I’m still having memory leak issues with the Music app, I’m saying it’s got nothing to do with it.
I haven’t done any of this, either.One thing that apparently does cause it is adjusting brightness manually or automatically while watching HDR Youtube videos.
Add Microsoft Outlook to this list and I'm not even running Monterey. Damn thing was hogging 3.65 gig AND IT'S JUST AN EMAIL PROGRAM!
I’ve never seen a bug like this on Mac OS so I’m going to hope they’re going to fix it next month at the latest. This is the worst bug I’ve ever seen that wasn’t data-destroying or bricking machines.Working on an important report I just ran out of memory using a MBP 14" 2021 with 32Gb of memory. Word was the culprit this time using 59Gb of memory! I have not changed my mouse setting or screen brightness settings. If this is not fixed soon I will have to revert to my Windows machine which I planned to sell. Being new to Apple I have no idea how quickly they release fixes but I am venting here as this needs to be fixed.
What is it about integrating Swift that causes memory leaks and more bugs?It's fallen off a cliff and the fact Apple are integrating more Swift will produce these results.
Just updated, will post results after a day or twoResolved in 12.1 or not?
from my other post..hello everyone, I'm 1h in with my prior rather problematic setup with Lightroom Classic and GPU acceleration On and what can I say, from here it looks ok. Still pretty high peaks from time to time but it regulates down so.
also chrome, safari both work fine with HDR content; the MS Office suite (teams, outlook, ppt, xls..) look fine as well via browser (office.365) --> Using a MacBook Pro 16", M1Pro, 32GB, 1TB..
well.. looks nice for my use case, I'll keep you posted![]()
So far so goodJust updated, will post results after a day or two
same here. over all memory pressure far far lower. From riding at 40-50% on 32gb w M1 Max to 17% after a day + uptime. Will keep checking it.So far so good
There’s no mention of fixing any memory leaks, but initial testing here suggests that at least two of the known leaks have been fixed, in coloured pointer and the Control Center, but not in Finder File/Find, which does still leak steadily.
Good pull.Oakley says there's still a leak in Finder:
What’s the source of this leak? It’s weird that it’s affecting multiple applications but it’s not fixed by one deeper bug fixOakley says there's still a leak in Finder: