MacBook Pro locks up with console message: UI updates were forcibly disabled by application "VMware Fusion"

[kevinp2]

I am running OSX Mavericks 10.9.5 and running Windows 7 from a Bootcamp partition using VmWare Fusion.

After upgrading to VmWare Fusion 8.0.2, if I leave the VM running for a few hours, the MacBook freezes up completely.  The mouse cursor moves, but nothing else functions.  I have to power off the Mac completely.

Invariably, in the Mac Console, I find this message a few seconds before the freeze occurred:

Nov  5 11:00:53 kpa04-2.local WindowServer[95]: disable_update_timeout: UI updates were forcibly disabled by application "VMware Fusion" for over 1.00 seconds. Server has re-enabled them.

This problem never happened with Vmware 6.  It is new to Vmware 8.  I am running only one VM with Windows 7, my bread and butter workstation.

If I do not start Vmware, the Mac runs for days at a time without any problem.  So this freeze is almost certainly caused by VmWare.

Any ideas for things to look at or change?  I have disabled App Nap and Shared Folders already.

Thanks in advance!

[Mikero]

Sorry to hear about the experience!

I don't have an answer, but perhaps our gurus can look into it.

Have you made sure to update Tools?

Can you also provide a support bundle? (help > Collect Support Information)

HPReg‌ lrucker‌

[kevinp2]

Hi, I did a Repair of the VMWare Tools and I'll see if that makes any difference.

I've attached the support bundle.

[HPReg]

When your machine freezes, your mouse still works, so interrupts still work, so networking probably still works and it is likely that only the WindowServer is hosed.

Something you might want to try: ssh into the frozen machine from another box. Then run the "sample" utility, from the remote shell, on the "VMware Fusion" process. This will likely tell us where the process is blocked, and what is going on.

[vanRijn]

Thanks very much for the support bundle, kevinp2!! Can you give us some more information on the exact scenario you're doing when this happens?

Do you see this behavior/crash for any other VM or only with the BootCamp VM?

Can you describe the exact steps you're taking before this happens?

What is your host monitor setup? Do you have only the built-in monitor or do you have external displays involved and if so, exactly what monitors and connections to those monitors?

What view mode are you using the VM in? Are you using Single Window mode, Fullscreen mode, Multimonitor Fullscreen mode, or Unity mode?

If you're seeing this crash when using the VM in fullscreen mode, do you see this problem if you use Single Window mode instead?

Thanks for your help!! =:)