Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
And another update..the usb problems actually got worse. I can no longer chain hubs.
That's what my problem is with the current release version (12.0.1)... I have a hub that will only work if it's connected to my USB-C dock (which itself I suppose is a hub). With Big Sur (and the i9 MBP... not sure which of those two is the culprit) I had this hub connected to another hub that was connected to the dock and it worked fine.
 
That's what my problem is with the current release version (12.0.1)... I have a hub that will only work if it's connected to my USB-C dock (which itself I suppose is a hub). With Big Sur (and the i9 MBP... not sure which of those two is the culprit) I had this hub connected to another hub that was connected to the dock and it worked fine.
This has been a problem since High Sierra. I have a Caldigit AV Pro 2 and a moshi USB 3.1 hub. It used to be the rMBP and now it's the iMac. Either machine won't start unless the moshi was connected to the Caldigit, which is an external HD and a USB hub. The computer would just hang on startup if I connect both directly to the USB port of the machine.

Thankfully, the way it would allow the computer to start is my preferred setup. Shopping for a USB hub for a Mac has become something of an art. o_O
 

Attachments

  • Screenshot 2021-11-10 at 08.16.13.png
    Screenshot 2021-11-10 at 08.16.13.png
    432.4 KB · Views: 97
This has been a problem since High Sierra. I have a Caldigit AV Pro 2 and a moshi USB 3.1 hub. It used to be the rMBP and now it's the iMac. Either machine won't start unless the moshi was connected to the Caldigit, which is an external HD and a USB hub. The computer would just hang on startup if I connect both directly to the USB port of the machine.
The chained hub configuration worked fine for me with the i9 on Big Sur. It's not a show-stopper, but my cable arrangement is a bit more awkward now.
 
Hmmm, trackpad gesture controls seem to no longer work when Safari is in focus. That's annoying.

For example, can't do 3 finger upwards swipe to show active windows, or three finger sideways swipe to change between apps. Putting safari out of focus fixes this.

just found out that it's probably connected to when the app is in fullscreen, in that scenario the finder/exposé completely loses it's mind and trackpad controls no longer works

Does it happen on all apps? Or are there workarounds if this happens ?? I'm considering upgrading to beta 2 from beta 1 since people said it has a better inertia scrolling fps than beta 1. Thanks!
 
The chained hub configuration worked fine for me with the i9 on Big Sur. It's not a show-stopper, but my cable arrangement is a bit more awkward now.
Yup, worked perfectly on intel/big sur. On M1/Monterey 12.0, 12.0.1 and 12.1 beta one it worked but mounting drives was horribly slow. Beta 2 chained docks/hubs no longer works (even thunderbolt).
 
Yes. I have it set to hide in both options (full screen/desktop) and have not run into this issue again. Bit of a shame on the new MBPs, I have just set it to always show but that's unworkable in this beta. Hope for a fix soon.
Yeah. I enabled the option to show it on fullscreen too. Really liked that. Hmm I'm still considering if it's worth disabling menu bar on full screen for the better scrolling inertia 120hz
 
Yeah. I enabled the option to show it on fullscreen too. Really liked that. Hmm I'm still considering if it's worth disabling menu bar on full screen for the better scrolling inertia 120hz
Ah that menu bar showing or not is just something that you get used to really. Now I don't miss it anymore lol.
 
Hopefully this will fix the random crashes I have been getting. At first I thought it was my Caldigit TS3 Thunderbolt hub that was causing the crashes, but then I unplugged that, and I just have my mouse, keyboard and external SSD drive on my MacMini M1 and I still get crashes. Even when nothing is loaded and the computer is sitting there idle, I'll come back and see that it's rebooted.

This is running 12.1 Beta (21C5021h)
 
Yup, worked perfectly on intel/big sur. On M1/Monterey 12.0, 12.0.1 and 12.1 beta one it worked but mounting drives was horribly slow. Beta 2 chained docks/hubs no longer works (even thunderbolt).
So wait, it's getting WORSE with the betas, not better?!? :(
 
I hope this is better for the 2021 14" MBP /16" MBP issues.

Overview​

The macOS 12.1 SDK provides support to develop apps for Mac computers running macOS Monterey 12.1 beta 2. The SDK comes bundled with Xcode 13.2 beta, available from Beta Software Downloads. For information on the compatibility requirements for Xcode 13.2, see Xcode 13.2 Beta Release Notes.

App Store​

New Features in macOS Monterey 12.1 beta 2​

  • StoreKit APIs that present a refund request sheet can be tested with StoreKit Testing in Xcode. Use beginRefundRequest(in:) or beginRefundRequest(for:in:) when working with AppKit or the refundRequestSheet(for:isPresented:eek:nDismiss:)view modifier when working with SwiftUI. (70794860)

iCloud Mail​

New Features in macOS Monterey 12.1 beta 2​

  • iCloud+ subscribers can now access and use Hide My Email directly from the Mail app. (84956894)

Safari Extensions​

Resolved in macOS Monterey 12.1 beta 2​

  • In Safari 15 and 15.1, sync storage for Safari Web Extensions is no longer being written into the local storage area. Developers using sync storage can check for storage in the local storage area if they can’t find their data in the sync storage area and do a one-time migration. (84214292)

SwiftUI​

Resolved in macOS Monterey 12.1 beta 2​

Known Issues​

  • Document-based apps include a Save As menu item above Duplicate. (83741212)


Holy ****. So still with memory leaks. ffs!
 
The first restart after I installed macOS Monterey (15.0.1), I got a warning stating that some extensions need to be updated before they'll work with the new operating system (Parallels Desktop, for example). In this article, hoakley mentioned that kernel leaks are partly due to third-party extensions:
Kernel memory leaks are not only more serious, but there’s usually nothing the user can do apart from restarting the Mac. Some do arise in third-party kernel extensions, so your first action should always be to uninstall all non-essential kernel extensions, but if they’re in one of Apple’s, or the kernel itself, all you can do is wait for Apple to fix it, once you’ve reported the problem with a panic log.

So for those who are experiencing severe memory leaks, maybe try:
  1. Removing all third-party kernel extensions and reinstalling them one by one so you can narrow down the culprit. Apple likely tweaked the macOS kernel again this time around.
  2. It seems people who use Adobe products and/or extensions that modify system-level functions, e.g. sound (e.g. utilities like SoundSource → SoundSource itself seems okay though), webcam input (e.g. utilities like EpocCam), keyboard mapping, and content blocker (utilities like Freedom) are the worst hit.
  3. Purge your memory manually.
Disclaimer: I'm not responsible for any data loss or damage to your machine as a result of you attempting any of the above steps.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.