Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Nice to know this is still there!

1639691005875.png
 
Safari is unusable on 12.1, I havent tried on 12.2 but its been unusable since Monterey was released. the CPU sits over 100% and the memory consumption grows and grows until the computer comes to a grinding halt. Ive switched to using the technology preview which doesnt have this issue, so maybe if they upgrade safari the issue will be gone?

How so?

Been using Safari to web build, drop box, we transfer, surf, not seen any issues on my 14’ MBP os12.1.
 
It was working in 12.1; it just wasn't perfect. It had jitters and stutters here and there and that is completely fixed and optimized in 12.2.
Thank you. Everyone that I've seen post about their experience in 12.1 says Promotion was working but still had stutters. Nobody said it was perfect and that it didn't need further optimizing. There's no need to make up narratives in here. We all want the same thing. Regardless, glad to see they optimized it further in 12.2
 
I’m over here with the base 16 inch and 16gb ram. No issues at all, not even an issue with playing rust over Rosetta.


Imagine watching the activity monitor all day waiting for swap to be used
Haha. Not watching activity monitor all day and im glad you are not having this issue but when WindowServer takes up that much memory, the machine becomes unresponsive and only a restart will temporarily fix it.
 
  • Like
Reactions: Danirosa
It seems quite responsive on the 2021 MacBook Pro. Hopefully it will fix the Wi-Fi issues I’ve been having as well.

Btw, is it me or Dolby Atmos sounds a bit different (testing it with AirPods Max). I feel like it’s more airy and I can hear more elements, but it might not be the case.

View attachment 1929530
Dang! Thanks for sharing. Such a nice and easy scroll.
 
Is there a memory leak in Safari?
For older versions, yes. I can literally watch via Stats (an open source version of iStat) as Safari 15.1's memory usage goes up moving total RAM usage going from 45% total to 80% (time to quit and restart Safari) and this is happening on Catalina. :( (That is as high as my late 2013 iMac can go)
Here is a picture of what it looks like when I reopen Safari with the exact same tabs before doing the quit-restart; note the cliff due to the memory that was "trapped" by the leak being let go (total usage was around 75%):
1639794037146.png
 
Last edited:
  • Like
Reactions: Kenjutsuz
It was working in 12.1; it just wasn't perfect. It had jitters and stutters here and there and that is completely fixed and optimized in 12.2.
Yeah, I'm talking about the people who would go to every thread saying "this is how it's supposed to be" when it clearly had issues
 
AppleInsider has reported that they are rebuilding Apple Music to use AppKit, instead of WebViews on 12.2. Something similar to that of the Apple TV app, which should increase performance, responsiveness, and efficiency.

Thank god. Even with the M1, the mac Music app has felt sluggish.
 
does anyone know if this build fixes the `cmd + tap` not registering on 14" MBP? As of the RC2 build I'm still having to tap 3 times for a link to open in the background. Several reports from people like this especially on the 14" MBP.
 
  • Sad
  • Like
Reactions: Traffy and racostaf
Im not personally seeing any bugs with 12.1 on my M1 MBP. Maybe you could post a massive list of all the bugs you are seeing? Many thanks

I’m sure the numerous forum posts can educate you.
 
Do tell, if you don't mind going into a bit more detail.
The search seems to be finally working! There are also some changes in the animations (things are sliding from the side, when opening a new pane).

Some of the issues I have come across so far is music not playing if you double click on the row (you have to specifically press the play button), the header in playlists does not stick to the top of the screen, there’s also problems with the back button when browsing the content.

I guess none of it is a big deal. They have time to fix it and the backend improvements will, hopefully, bring the difference we are waiting for. Even if not everything is ready for the 12.2 release, moving to native components should give much more flexibility in future for implementing new features and ensuring better stability (or at least I hope so).
 
There are differences, bit also some new issues.
One thing I'm curious about is if they've finally fixed queueing when listening to a radio station. If you right click and say "Play Next", it doesn't play it next if you're listening to a radio station.

This is unlike on iOS where it correctly plays that track next, then resumes with the radio station.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.