Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
An operating system contains millions of lines of code. It will never be perfect and there will always be some memory leak somewhere. But the major ones seem to be under control.
I work in software Quality Assurance and I can guarantee you that perfect software does not exist!
I'm not sure that it's necessarily accurate to say that there will "always" be memory leaks
 
  • Haha
Reactions: Babygotfont
12.2 fixed the major memory leak issue, I have been on 12.3 on two machines on a full time basis for work with zero issues.
I still have issues with Safari tabs gobbling up as much as 3GB each. Also Google Drive showing up as much as 70GB in Activity Monitor even when I have only 16GB of memory on my m1 iMac. If I force quit it, it drops memory usage down from like 14 to around 9GB. I know , that doesn't explain the 70GB , but.... If I use Brave Browser, I have none of the Safari issues.
 
  • Wow
Reactions: Babygotfont
my m1 max 16" is dropping batt 1% like every min, and kernel_task is showing 500 plus threads what's happened my batt was amazing before
Similar issues with my 2018 13"" Intel Macbook Pro with kernel_task taking over 700% of my CPU with 200 plus threads. Never had this issue before I installed macOS 12.3 but the problem remains even after updating to 12.3.1 Any ideas on what's causing this?
 
  • Haha
Reactions: Babygotfont
See here maybe it will be of help:
Thanks for this! Unfortunately, I'm still not able to figure out why kernel_task is hogging over 700 % CPU on my Macbook Pro. It seems like it's related to the update to macOS 12.3 as the problems started when I updated to it but I created another new user on my Macbook from scratch to play with on my Mac with no apps installed there apart from the basic Apple ones and there were no issues there. So it seems there's something wrong with the software on my MAcbook which is interacting in this manner but I haven't installed or updated anything major in the last week or so since when these problems started
 
  • Sad
Reactions: Babygotfont
This 12.3.1 has improved waking screens on M1 Mac mini dramatically (I do have the computer set not to sleep, just the screens) - used to flash on and off 2-3 times when the screens were waking up in earlier OS versions - and sometimes my 2nd screen an LG 27" IPS screen would go solid blue. Since installing 12.3.1 the screens waking up once, and haven't had the 2nd screen go blue.
On 2018 Mac mini it has improved screens waking from sleep as well, still flash once, but overall a better experience than before. (not quite as improved as the M1 Mac mini though)
 
  • Wow
Reactions: Babygotfont
I had my first crash when waking from sleep with a hdmi monitor attached with 12.3, I switched to USB C and didn't have the issue. I ran the update today, now the USB C monitor sees no signal. macbook pro m1. I've tried multiple ports. Awesome.
 
This 12.3.1 has improved waking screens on M1 Mac mini dramatically (I do have the computer set not to sleep, just the screens) - used to flash on and off 2-3 times when the screens were waking up in earlier OS versions - and sometimes my 2nd screen an LG 27" IPS screen would go solid blue. Since installing 12.3.1 the screens waking up once, and haven't had the 2nd screen go blue.
On 2018 Mac mini it has improved screens waking from sleep as well, still flash once, but overall a better experience than before. (not quite as improved as the M1 Mac mini though)
iMac 2020 5700XT one over here.

If I restart or boot the computer I have to make sure to disconnect the two TB Display screens… else the computer gets stuck forever at the white Apple logo boot sequence. It isn’t as horrible as the screens are daisy chained so only one cable for a few seconds then plug back until next reboot, but it raises eyebrows about what other bugs could be happening sneakily.

Besides that, this update has revived the performance for me. It has regained some of the snappiness specially when manipulating windows, desktops switches, Mission Control, etc… macOS 12 was frustratingly messy on this front for me.
 
I had to re-install Monterey at the beginning of the year (hard drive failure). From that moment on, I had two fairly annoying bugs that survived multiple OS updates but this release finally fixed:
  1. I would be pestered over and over to allow the OS and many apps to use my location every time I rebooted.
  2. My desktop icon thumbnails stopped rendering.
I tried everything to fix those issues and finally surrendered. Multiple threads on Apple's forums where other users tried unsuccessfully to fix #1 particularly. Even Apple support and OS re-installations didn't fix it for them (I never bothered trying because of those posts). I was pleasantly surprised that both issues seem to be resolved when I signed in this morning after last night's update.
 
Universal Control on my MacBook Pro M1 Max with MacOS 12.3 was working great with my iPad using the latest beta, iPadOS 15.5. But after upgrading my MacBook Pro M1 Max to MacOS 12.3.1 Universal Control no longer works at all. Disappointed. Has anyone found a workaround?
 
Universal Control on my MacBook Pro M1 Max with MacOS 12.3 was working great with my iPad using the latest beta, iPadOS 15.5. But after upgrading my MacBook Pro M1 Max to MacOS 12.3.1 Universal Control no longer works at all. Disappointed. Has anyone found a workaround?
I think the only "workaround" is to install macOS 12.4 beta too - it states in the iPadOS 15.5 beta release notes that Universal Control isn't compatible with iPadOS 15.4 / macOS 12.3:

Universal Control​

Known Issues​

  • Universal Control in this release isn’t compatible with macOS 12.3 and iOS 15.4.
    Workaround: Use Universal Control between macOS 12.4 beta and iOS 15.5. (91136128)
 
  • Like
Reactions: rungxanh2901
Have tried several time install it. Downloads and goes through the complete steps but won't install. Installed on my other 2013 trashcan with no problem. Both computers the same with the exception of memory.
 
I think the only "workaround" is to install macOS 12.4 beta too - it states in the iPadOS 15.5 beta release notes that Universal Control isn't compatible with iPadOS 15.4 / macOS 12.3:

Universal Control​

Known Issues​

  • Universal Control in this release isn’t compatible with macOS 12.3 and iOS 15.4.
    Workaround: Use Universal Control between macOS 12.4 beta and iOS 15.5. (91136128)
Thank you. I wish I had read that before I updated my iPad. So I guess I'll just wait for the next update and hope it comes back.
 
I was having the problem of my Thunderbolt Display not waking up on my 2013 Mac Pro 6.1. I would have to unplug the display from the power bar (since the monitor has no on/off switch) then plug it back in. All seems to have been resolved with the 12.3.1 update... and I thought it was a hardware problem... silly boy.
 
Thanks for this! Unfortunately, I'm still not able to figure out why kernel_task is hogging over 700 % CPU on my Macbook Pro. It seems like it's related to the update to macOS 12.3 as the problems started when I updated to it but I created another new user on my Macbook from scratch to play with on my Mac with no apps installed there apart from the basic Apple ones and there were no issues there. So it seems there's something wrong with the software on my MAcbook which is interacting in this manner but I haven't installed or updated anything major in the last week or so since when these problems started

Kernel task running at absurdly high percentages usually indicates that the SMC has lost contact with a thermal sensor. Kernel task does this as a failsafe measure to prevent further overheating. Are your fans also running at full speed? That's about as far as my knowledge goes but I an certain that other, brainier users, can take this idea and run with it (or discredit it).
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.