What’s their reasoning for doing that? Wasn’t ObjC more than capable?It's fallen off a cliff and the fact Apple are integrating more Swift will produce these results.
You will probably won't want this because it is not application's fault it seems and killing something while in use can give other kinds of problems. Imagine having iMovie using more ram and it gets killed. Then you will have to repair the library.Can’t someone make a shortcut that checks activity monitor and force quits processes with excessive memory usage? ?
Good point, though I wasn’t serious. So shortcut should only kill certain tasks that keep getting mentioned like Control Center, kernel_task, callservicesd, etcYou will probably won't want this because it is not application's fault it seems and killing something while in use can give other kinds of problems. Imagine having iMovie using more ram and it gets killed. Then you will have to repair the library.
I believe until this problem is fixed the only thing we can do is keep monitoring memory usage and maybe restart that aplication and if not possible, the OS.
That’s discretion, not laziness. I on the other hand ordered a MacBook so it’s Monterey or bust for me. But I’m holding on to my trade-in as long as possible for backupffs never have I been more grateful at my laziness at having not upgraded.
How could they ship something with this 'level' of bug? After all the betas??
****ing outrageous.Don't bother with the 12.1 beta if you think it has a fix for the "memory leaks" issues.
In my case the Control Center memory usage seems to grow the more video you play. For example using DaVinci Resolve or watching something with Apple TV+.
fView attachment 1903786
Had the same issue on M1 in Beta months ago and reported it, was so bad back then I couldn't use Monterey for work because Chrome would crash the 16 GB system, recently while working I've almost crippled Monterey working in Chrome with 7-8 tabs.Just for additional information - I started experiencing these issues with a beta version of Monterey, released in August. I was using the 16" MacBook Pro (Intel) back then. I am also experiencing memory leaks on the new 16' MacBook Pro and the 2021 iMac. I know these issues might be hard to find and fix, but it's been happening for the past three months and I really wish Apple focused on that issue as a priority. Releasing Monterey with a critical bug like this was not the best thing to do.
Oh that's just Chrome's normal behaviorPlease add Google Chrome to the list. That’s the bread winner!
Apple needs to urgently release a new update for the macOS Monterey.
This whole thing is a sh**-show.
Am I exhibiting child-level optimism and naivety in wondering if it will be fixed in the first update....
This is gold. ?My Apple Music is trying to steal the memory hoarder throne from Google Chrome
View attachment 1906450
There is no such thing as a „good memory cleaner“. “Memory cleaners“ are little more than snake oil and are pretty much useless, they do more harm than good. Better stay awayDoes anyone know a good memory cleaner? One expensive I was not anticipating with 32Gb of RAM.
Bingo. Best option is open terminal and do 'sudo purge'. But don't know if that will solve this particular problem.There is no such thing as a „good memory cleaner“. “Memory cleaners“ are little more than snake oil and are pretty much useless, they do more harm than good. Better stay away