Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Yeah, I think this weill be the final update. Reminds me of an old Steve Jobs line about Blu-ray being a "bag o hurt."

I think Tim Cook wants to get away from this dumpster fire as quickly as possible and move onto Big Sur and Apple Silicon and pretend it didn't happen. Similar to how they moved quickly on IOS to get rid of 32 bit apps, pretend you never had them or needed them.
 
  • Like
Reactions: johnalan
I actually experienced the virtualization bug for the first time today, so the timing here is perfect.
This issue was not effecting all computers, only some models more so, I only saw it on a late 2015 iMac 27", not on a MBP laptop but it occurred fairly quickly with any activity that was both sustained CPU/GPU intensive. I went though extended diagnostics with 3rd party tools to make sure it was nothing hardware wise then started submitting feedback to Apple with attachments. At the same time sent all the auto crash report sends to apple. It literally occurred almost two dozen times as my experience. So only once, glad you didn't experience the worse. ;)
 
  • Like
Reactions: greenvomit8
I hope it does something about this too, i.e. the ”com.apple.driver.watchdog” related panic:

 
I’ve felt “washed out” when starting up in the morning as well :p

The article of course means that the display appears washed out, not “the Mac.” But we all know that, naturally...
 
I've been a Mac user for almost 20 years yet this is the first time I have never updated my systems to the latest OS. I've held off on 10.15 but am considering updating as Apple has begun to drop support for certain aspects of 10.14 (security updates, etc will continue of course). I've been experiencing issues on two Mac Pro's that haven't been resolved with weeks of online research, clean installs, and Apple tech leading me to consider updating to 10.15.

My biggest concern is access to root as Apple continues to extend SIP. I've always disabled SIP and Gatekeeper as I require read/write access for development and third party apps. Certainly this it not something everyone should do and doing so is always with risk yet is a necessity for my personal needs and I utilize other precautions, etc.

That stated, my biggest concern is read/write access to root as Apple created two volumes for Applications - User and System. I've created a script that mounts the drive for read/write, assigns the necessary permissions, then deletes it. I've used this on my MacBook Pro for development work which is now running Big Sur.

My concerns with 10.15:

- Will this be necessary in case my system needs to be restarted? (I rarely do so unless necessary)
- Has Apple locked the ability to mount and change root permissions with incremental 10.15.x updates?

Don't even get me started on Big Sur. Running it on my MacBook Pro for development and struggling to adjust to the UI in addition to SSV. I completely understand Apple's focus on security especially for novices/everyday users, yet their focus on locking the system down further with each release makes it difficult for third party developers to maintain their apps which is most likely Apple's true intentions as they want to force developers to utilize the Mac App Store. Given there are ways to easily bypass Apple's security measures - granted they've made the processes more difficult - and users have already found backdoors in Big Sur, I wonder if there are better methods for security measures than what Apple has been implementing since SIP and Gatekeeper were introduced.

I don't know what "SSV" stands for, the rest of your concerns sounds valid, but with Mojave you have another year of security updates and with Catalina you have only 1 more year, so the difference is incremental anyway. Extremely short support cycle, and even Big Sur will see the end of support in 3 years, and time passes quickly.
 
  • Like
Reactions: CJ Dorschel


Apple today released a supplemental update for macOS Catalina 10.15.6, with the update coming a month after the ...
It also fixes an issue that could cause the 2020 iMac to appear washed out after waking from sleep...

This issue also effects the 2019 MBP 16 Inch, I thought my display took a dump on me the day after I got the unit back from apple from the screen shattering.
 
I had hopes for this update, even though I hadn't been having issues with VMWare. I was hoping it would fix the Mac mini/eGPU issues. But in fact, the update made it worse. My mini completely freezes up upon booting now (if the eGPU is connected). So I'm just leaving my eGPU disconnected and hoping Big Sur fixes it.
 
I don't know what "SSV" stands for, the rest of your concerns sounds valid, but with Mojave you have another year of security updates and with Catalina you have only 1 more year, so the difference is incremental anyway. Extremely short support cycle, and even Big Sur will see the end of support in 3 years, and time passes quickly.

Thank you for the informative reply and taking my request seriously. It's refreshing to know there are people here who truly want to be helpful. :)

As for SSV: it's "Signed System Volume". Here's a decent article that covers much of this topic.

 
  • Like
Reactions: star-affinity
That's because your comment sounded like a subtle irony that I took time and insight to appreciate because, obviously, neither I nor anybody here can't help with such fundamental issues rather than blabbing about that.
 
  • Like
Reactions: CJ Dorschel
That's because your comment sounded like a subtle irony that I took time and insight to appreciate because, obviously, neither I nor anybody here can't help with such fundamental issues rather than blabbing about that.

Understood. My question was for those who have been using Mojave as I have not, hence others can fundamentally answer my initial inquiry. It also stems from research as Apple has changed the ability to access root with some 10.15.x updates but developers and users were able to resolve the issue after release. If I were to update now, it would be with this update as I do not have a previous version of Mojave saved on my array, hence why I asked if anyone was experiencing this issue again as many of us are in the same predicament. That's all.
 
According to Apple's release notes, the update fixes a problem that could cause virtualization apps like VMware to crash.

It was not just virtualisation apps. It was a much wider kernel memory leak which caused problems with multiple apps using kexts and/or their more recent replacements. Hopefully they are all fixed, but will wait a day to see how things go.
 
Thank you for the kind assistance. My question was simple and I'm not in an "intellectual trap". If you have nothing productive to add to a discussion, perhaps it's best to be an adult and refrain from unnecessary slights.

I find that a little ironic given your complaint has nothing to do with the memory leak discussed in the article. You’re voicing concerns that the locked down nature of recent macOS releases makes your particular workflow hard, but I don’t see how that adds something “productive” to this bug, and the way Apple has handled it.
 
Yes, and you’re saying I’m a terrible dev. Got it.

Sure, that’ll improve morale.
I’ve no idea about your competence as a developer as I really am indifferent. When you have a process escape of this magnitude then doing nothing is not an option. Apple‘s reputation is battered by this one. That it took a third party vendor to find it is a terrible indictment of Apple’s development process.
 
Yet another update to Catalina with no mention of the Mail app bugs that have kept me from upgrading all this time.

Can anyone confirm whether the issue of email data loss via Mail app has been definitively fixed or not?
 
I’ve no idea about your competence as a developer as I really am indifferent. When you have a process escape of this magnitude then doing nothing is not an option. Apple‘s reputation is battered by this one. That it took a third party vendor to find it is a terrible indictment of Apple’s development process.

We don’t know if it took VMware to find it, to escalate it, etc. We do know someone thought it not severe enough not to ship the release, which was perhaps the wrong call.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.