Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Generic User Avatar

Heads up, macOS Sanoma 14.4 have bugs that can cause issues


  • Please log in to reply
6 replies to this topic

#1 Chiragroop

Chiragroop

  •  Avatar image
  • Members
  • 428 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:07:21 AM

Posted 24 March 2024 - 06:12 PM

If you are running Sanoma and are running into USB hubs issues or issues with devices plugged into a port, apps that use Java, printer issues, iLok software or can't find older versions of files stored in iCloud Drive with optimized storage on, this is due to bugs in macOS 14.4 https://www.macrumors.com/2024/03/18/do-not-update-macos-sonoma-14-4/

 

If you are running older version, stay there or upgrade to 14.3.1 only until Apple releases a fix.



BC AdBot (Login to Remove)

 


#2 greg18

greg18

  •  Avatar image
  • Members
  • 1,743 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Los Angeles, CA
  • Local time:09:21 AM

Posted 24 March 2024 - 06:33 PM

There is no issue since it is newer security protocols that require you to authorize the accessory. It is the same as what is done in iOS to secure the USB port. I run MacOS 14.4 developer and have not had any USB device issues.

 

Oracle is behind on Apple on getting their software up to date with the latest changes. Also older hardware is going to have problems with more modern, more secured Operating Systems.



#3 Chiragroop

Chiragroop
  • Topic Starter

  •  Avatar image
  • Members
  • 428 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:07:21 AM

Posted 24 March 2024 - 06:48 PM

As for Oracle, that is because of a bug in macOS 14.4. A memory access on a protected memory region created with mmap should result in SIGBUS or SIGSEGV results in SIGKILL in macOS 14.4. This unannounced change is a bug due to Apple not testing their changes while adding support for JIT for third-party apps in iOS 17.4 and accidentally bringing this change over.


Edited by Chiragroop, 24 March 2024 - 08:12 PM.


#4 greg18

greg18

  •  Avatar image
  • Members
  • 1,743 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Los Angeles, CA
  • Local time:09:21 AM

Posted 25 March 2024 - 08:48 AM

Again it is not a bug of the OS, it is Oracle not having their software ready when they have had access to the code way before even developers have had access to it.

Apple does not have to test the code of third party software, it is up to the third party software coders to check their code

Edited by greg18, 25 March 2024 - 08:49 AM.


#5 Chiragroop

Chiragroop
  • Topic Starter

  •  Avatar image
  • Members
  • 428 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:07:21 AM

Posted 25 March 2024 - 02:13 PM

Again it is not a bug of the OS, it is Oracle not having their software ready when they have had access to the code way before even developers have had access to it.

Apple does not have to test the code of third party software, it is up to the third party software coders to check their code


It was very much a bug in macOS which Apple just fixed with macOS 14.4.1 released today. As stated in the release notes:

  • USB hubs connected to external displays may not be recognized.
  • Copy-protected Audio Unit plug-ins designed for professional music apps may not open or pass validation.
  • Apps that include Java may quit unexpectedly.

Oracle couldn't even use the developer preview to test this because Apple changed the SIGBUS and SIGSEGV to SIGKILL in the release version. As Oracle stated in their blogpost

The issue was not present in the early access releases for macOS 14.4, so it was discovered only after Apple released the update.

I just don't understand why you are arguing that an OS bug isn't an OS bug when both Apple and Oracle acknowledged it. There have been bugs in different OSes before too.



#6 greg18

greg18

  •  Avatar image
  • Members
  • 1,743 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Los Angeles, CA
  • Local time:09:21 AM

Posted 26 March 2024 - 05:41 AM

Again it is not a bug in Mac OS, it is a third party hardware that is outdated, Oracle is not getting their stuff out in time for developers.

#7 Chiragroop

Chiragroop
  • Topic Starter

  •  Avatar image
  • Members
  • 428 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:07:21 AM

Posted 26 March 2024 - 06:48 AM

Apple agreed it was an OS bug. Oracle agreed it was an OS bug. If you understood the bug you would know it was an OS bug. Apple even fixed the bug. Third-party docks weren't outdated. You are just here to argue

Edited by Chiragroop, 26 March 2024 - 07:18 AM.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users