Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
VMware Engineer Confirms macOS Catalina 10.15.6 Bug Causes Crashes with Virtualization
- Thread starter MacRumors
- Start date
- Sort by reaction score
Can someone comment on the underlying virtualization methods used by Virtualbox, VMware and Parallels? Seems that there are several accounts of Parallels being unaffected by this issue. I'm curious if there is an underlying puyblished difference.
The article says, "A regression in the App Sandbox component of macOS 10.15.6 is reportedly leaking kernel memory, causing macOS to crash. The purpose of an App Sandbox is to provide protection to system resources and limit an app's access to resources, such as memory."
I wonder if Parallels doesn't use the App Sandbox at all? That WOULD explain it. It's also why I asked earlier about which versions of VMware people were running. I had a thought that earlier versions of VMware Fusion might not exploit the buggy feature (though I've 8.5.x on a 10.15.6 laptop and I'm pretty sure the symptoms of a kmem leak are there).
I am using the latest Fusion Pro version and build, but have not encountered the bug because I shut my machines down after testing and working with them. They are probably just not up long enough to kill my host OS.
At this point, I am just lucky. I don't need any trouble at this point, so I am contemplating a move to Parallels.
At this point, I am just lucky. I don't need any trouble at this point, so I am contemplating a move to Parallels.
A leak of this sort should be unacceptable. Prior posters mentioning it's probably all-hands-on-deck for Big Sur might explain why we haven't seen a supplemental update for this already. Such a bug, IMHO, really deserves a quick fix.
Agree completely. I hope Apple releases a supplemental on this issue. I'd like to keep using Fusion since I keep buying it every release.
I was also caught up in a bluetooth bug in Fusion Pro 10 a year ago or so that VMware neglected to fix for months on end. That really impacted my current workflow of starting and stopping machines because it would kill the bluetooth module almost everytime I started a VM. They finally fixed it.
nope.
Same for me as well. Running Catalina on 2017 MBP 13” Win10Pro 64bit.
the only issue I have is the odd and random left-mouse-click becomes right clicking andthen begins full screenshot with either Left/Right click; very annoying. Logi Anywhere 2S mouse with TB3 to usb (Apple) adapter. Has nothing to do with my VM in Parallels with Windows.
Does anyone know why Debian Linux was chosen at WWDC 2020? I’ve seen spins of various Linux for Arm, just curious why Debian distro was chosen.
Found a large post on VMware communities about this. Some interesting thoughts and help.
Around page 6 folks in the thread are talking about downgrading.
Around page 6 folks in the thread are talking about downgrading.
After reading some more posts since my last visit, seems like this issue affects some, but not everyone. I am starting to wonder for those who need windows, and a VM isn't a stable solution, if it's time to bite the bullet and use bootcamp and run it natively. At least until this issue is sorted out. I still haven't had issues, but I don't run a VM very often, but when I do, haven't had issues. I'm also thinking ahead to after Apple switches to ARM, if people need another OS, if it's maybe the time to finally look into either a dual boot, or, a second computer at least that's dedicated to that OS. I have always liked the ease of use VMs provide by allowing multiple systems to run without a reboot, but at the same time, it can have it's drawbacks, as people are finding out more and more lately it seems with these problems cropping up, and Apple's transition. For those asking about big Sur, currently the word is, NO Virtualization software works.
I think I remember hearing that, which is good, i was really directing that comment to the general public that doesn't have access to that, and may need to use a VM now, before the new release is public.
I don’t really follow, since Big Sur itself is still in beta anyway.
This is unrelated to the bug in Catalina.
Two kernel panics yesterday after fresh reboots from the am. Fans blazing, black screened- force shutdown.
Man this is really a problem for me, as I run VMware every day for a couple of required programs. Calling Apple today.
Man this is really a problem for me, as I run VMware every day for a couple of required programs. Calling Apple today.
Best bet is probably to restore from a 10.15.5 backup.
(I haven't upgraded to 10.5.6 yet and am kinda scared to.)
I hadn't seen this issue when using Parallels Desktop, or so I thought. It turns out that the issue does appear for Parallels, at least for me. The reason I didn't see it manifested as quickly as others is that I have 64GB of RAM on my iMac. It just took longer to show up as it chews through the RAM. I do have RAM cleaners that buy some time (Memory Clean2 and Parallels Toolbox's Free Memory), but eventually, I have to reboot my Mac about once a week.
I wonder how long it's going to take Apple to release a fix for this. It's a pretty major problem.
I wonder how long it's going to take Apple to release a fix for this. It's a pretty major problem.
A person who goes by DanielDarko on the VMware Fusion community forum that I was referring to ealier has posted something interesting.
From that forum
-------------
115. Re: VM Ware Fusion potentially causes macOS 10.15.6 to crash
![DanieDarko]( "DanieDarko")
DanieDarko Aug 6, 2020 7:05 AM (in response to JavierIBM)
I'm using virtualbox and been experiencing the same issue.
After several crashes (2-3 each day), I too figured out the kernel memory leak problem since 10.15.6 update.
Now that I'm aware that the com.apple.security.sandbox Kext is actually causing the memory leak, I'm eager to find a workaround.
As a workaround I did copy the /System/Library/Extensions/Sandbox.kext from 10.15.5 to my Macbook running 10.15.6.
For now it's running without any problems and the memory leak seems to be resolved.
I will keep my Windows 10 guest running and post any updates.
--------------
123. Re: VM Ware Fusion potentially causes macOS 10.15.6 to crash
![DanieDarko]( "DanieDarko")
DanieDarko Aug 6, 2020 10:39 AM (in response to amjbecker)
Just did this myself and can confirm, the Sandbox.kext can be extracted from macOS Combo update 10.15.5:
https://updates.cdn-apple.com/2020/macos/001-12346-20200528-c8559404-82ce-4926-a8cf-a2ff6630fe44/macOSUpdCombo10.15.5.dm…
Just extract it with pkgutil --expand-full macOSUpdCombo10.15.5.pkg
or to extract it with any other util and extract macOSUpdCombo10.15.5.pkg/Payload using pbzx.
Afterwards you should have the System/Library/Extensions/Sandbox.kext and usr/libexec/sandboxd directory structures.
sandboxd also differs, so maybe it's a good idea to replace both...
To replace them just save these files somewhere on your disk and reboot into recovery mode, holding Cmd+R.
Then you just need to mount your system disk using Disk utility and then launch the terminal to copy the files into place.
Don't forget to check the ownership and permissions!
------------
I think I am going to take a solid backup and attempt this until Apple deals with this issue.
From that forum
-------------
115. Re: VM Ware Fusion potentially causes macOS 10.15.6 to crash
DanieDarko Aug 6, 2020 7:05 AM (in response to JavierIBM)
I'm using virtualbox and been experiencing the same issue.
After several crashes (2-3 each day), I too figured out the kernel memory leak problem since 10.15.6 update.
Now that I'm aware that the com.apple.security.sandbox Kext is actually causing the memory leak, I'm eager to find a workaround.
As a workaround I did copy the /System/Library/Extensions/Sandbox.kext from 10.15.5 to my Macbook running 10.15.6.
For now it's running without any problems and the memory leak seems to be resolved.
I will keep my Windows 10 guest running and post any updates.
--------------
123. Re: VM Ware Fusion potentially causes macOS 10.15.6 to crash
DanieDarko Aug 6, 2020 10:39 AM (in response to amjbecker)
Just did this myself and can confirm, the Sandbox.kext can be extracted from macOS Combo update 10.15.5:
https://updates.cdn-apple.com/2020/macos/001-12346-20200528-c8559404-82ce-4926-a8cf-a2ff6630fe44/macOSUpdCombo10.15.5.dm…
Just extract it with pkgutil --expand-full macOSUpdCombo10.15.5.pkg
or to extract it with any other util and extract macOSUpdCombo10.15.5.pkg/Payload using pbzx.
Afterwards you should have the System/Library/Extensions/Sandbox.kext and usr/libexec/sandboxd directory structures.
sandboxd also differs, so maybe it's a good idea to replace both...
To replace them just save these files somewhere on your disk and reboot into recovery mode, holding Cmd+R.
Then you just need to mount your system disk using Disk utility and then launch the terminal to copy the files into place.
Don't forget to check the ownership and permissions!
------------
I think I am going to take a solid backup and attempt this until Apple deals with this issue.
It's not a VMware problem to fix. Apple has to fix it. 11.5.6 doesn't change that- the problem is still listed as a known issue.
I was curious, without reading back through the whole thread, does anyone happen to know if this issue affects ALL macs running 10.15.6, or is it say, only newer computers that say have the T series chips, and the newer hardware? I ask because, I've seen other cases where people who have had issues with Catalina only have them on newer macs, while older hardware seems unaffected. Now, this is a hit and miss scenario depending on the issue, and person's environment. It perked my curiosity because, after the initial first releases of Catalina, with the new release bugs, things have been rock solid here. Sure i'll have glitches once and a while, but nothing show stopping, at least not like it was initially. As I said in earlier post, the main issues I've had with a VM package, that even remotely border on the one mentioned here was with VirtualBox, and that did cause kernel panics. The worst issue, I've personally had with Fusion was with Bluetooth mice and keyboards, going between a VM and host would cause the devices to stop working for several seconds. mainly on launch and quit of the Fusion app. Lately, that seems to have been resolved some time back. However, I'll keep posted if i discovery anything specific here.
VMWare confirms the update does not fx the problem. As said above, it's an Apple problem to fix.
It's not related to the T1/T2. It's a memory leak in the sandbox which affects any Mac.
OK, yes, I was aware of it being related to memory and sandbox, I was simply curious if newer machines with newer RAM, and the T2 handled those things differently compared to the older ones. Sounds like this particular issue is the same regardless the hardware generation.