Fusion Professional Version 8.0.1 crashes on OSX 10.11

[Elpres]

Almost always when I try to open Fusion it crashes

Application Specific Information:

*** Terminating app due to uncaught exception 'CALayerInvalidGeometry', reason: 'CALayer position contains NaN: [nan nan]'

*** multi-threaded process forked ***

terminating with uncaught exception of type NSException

crashed on child side of fork pre-exec

I can provide a full crash report if necessary but it seems to be related to multiple virtual desktops. I have encountered the issue while having 1 or 2 virtual desktops. It seems to be fixed when I add and remove back to only having 1.

[uGpYu3f9xJDC]

I had the same issue: always when I started the VM that used to switch to full-screen mode VMware crashes with the same crash report.

Maybe it's related to a different monitor configuration.

Somehow it worked now. The only thing I changed was that I enabled the "Use full resolution for Retina display" checkbox in Display settings of the VM and after the next crash disabled it again.

[tomagochi]

I had the same issue and try the two suggestions above. None of them works for me. The only way to run Fusion is to disable the distincts spaces option in Mission Control which is mandatory for the split view feature !

I hope the issue will be fixed in the next release,

Tom

[robbedoes]

Same fusion 8.0.1 crashes on startup of fusion in OSX 10.11. No workable situation.

I went back to fusion 7.1.2. This version doesn't support multiple monitor under osx 10.11, but Unity mode does work.

Please update both 7.x and 8.x for OSX 10.11

I now spent money for something I can't use ...

[sapridyne]

Same issue here. Really annoying and disappointing.

[joenall]

Happening frequently here as well. Very unstable.

Process:               VMware Fusion [1286]

Path:                  /Applications/VMware Fusion.app/Contents/MacOS/VMware Fusion

Identifier:            VMware Fusion

Version:               8.0.1 (3094680)

Code Type:             X86-64 (Native)

Parent Process:        ??? [1177]

Responsible:           VMware Fusion [1286]

User ID:               501

Date/Time:             2015-10-15 14:57:22.568 -0500

OS Version:            Mac OS X 10.11 (15A284)

Report Version:        11

Anonymous UUID:        E67E43F2-D40C-E0B6-CDF6-245924C53599

Time Awake Since Boot: 970 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)

Exception Codes:       0x0000000000000000, 0x0000000000000000

Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:

*** Terminating app due to uncaught exception 'CALayerInvalidGeometry', reason: 'CALayer position contains NaN: [nan nan]'

*** multi-threaded process forked ***

terminating with uncaught exception of type NSException

crashed on child side of fork pre-exec

Application Specific Backtrace 1:

0   CoreFoundation                      0x00007fff97b33bd2 __exceptionPreprocess + 178

1   libobjc.A.dylib                     0x00007fff98a83dd4 objc_exception_throw + 48

2   CoreFoundation                      0x00007fff97b9a3fd +[NSException raise:format:] + 205

3   QuartzCore                          0x00007fff8bc8735e _ZN2CA5Layer12set_positionERKNS_4Vec2IdEEb + 152

4   QuartzCore                          0x00007fff8bc872be -[CALayer setPosition:] + 44

5   QuartzCore                          0x00007fff8bc885d0 -[CALayer setFrame:] + 648

6   AppKit                              0x00007fff86cdc015 __100-[_NSFullScreenTransitionOverlayWindow startEnterFullScreenAnimationWithDuration:completionHandler:]_block_invoke + 513

7   libdispatch.dylib                   0x00007fff990ce8ff _dispatch_call_block_and_release + 12

8   libdispatch.dylib                   0x00007fff990c3453 _dispatch_client_callout + 8

9   libdispatch.dylib                   0x00007fff990d6c1c _dispatch_main_queue_callback_4CF + 1685

10  CoreFoundation                      0x00007fff97ae9789 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9

11  CoreFoundation                      0x00007fff97aa873d __CFRunLoopRun + 1949

12  CoreFoundation                      0x00007fff97aa7d38 CFRunLoopRunSpecific + 296

13  HIToolbox                           0x00007fff99331d55 RunCurrentEventLoopInMode + 235

14  HIToolbox                           0x00007fff99331b8f ReceiveNextEventCommon + 432

15  HIToolbox                           0x00007fff993319cf _BlockUntilNextEventMatchingListInModeWithFilter + 71

16  AppKit                              0x00007fff869acf3a _DPSNextEvent + 1067

17  AppKit                              0x00007fff869ac369 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454

18  AppKit                              0x00007fff869a0ecc -[NSApplication run] + 682

19  AppKit                              0x00007fff8696a162 NSApplicationMain + 1176

20  VMware Fusion                       0x000000010d0b499f VMware Fusion + 47519

21  libdyld.dylib                       0x00007fff9513c5ad start + 1

22  ???                                 0x0000000000000002 0x0 + 2

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0   libsystem_kernel.dylib         0x00007fff864d50ae __pthread_kill + 10

1   libsystem_pthread.dylib       0x00007fff924ce500 pthread_kill + 90

2   libvmwarebase.dylib           0x000000010e6b97d3 SigCoreDumpViaChild + 963

3   libvmwarebase.dylib           0x000000010e6b9987 Sig_CoreDump + 39

4   libvmwarebase.dylib           0x000000010e43f8ed Panic_Panic + 141

5   libvmwarebase.dylib           0x000000010e43fa52 Panic + 130

6   libvmwarebase.dylib           0x000000010e6b8c20 0x10e3f4000 + 2903072

7   libsystem_platform.dylib       0x00007fff8ac0052a _sigtramp + 26

8   ???                           0x0000000088fdf35d 0 + 2298344285

9   libsystem_c.dylib             0x00007fff88fce37b abort + 129

10  libc++abi.dylib               0x00007fff93bf5f81 abort_message + 257

11  libc++abi.dylib               0x00007fff93c1ba47 default_terminate_handler() + 267

12  libobjc.A.dylib               0x00007fff98a8708d _objc_terminate() + 103

13  libc++abi.dylib               0x00007fff93c1919e std::__terminate(void (*)()) + 8

14  libc++abi.dylib               0x00007fff93c19213 std::terminate() + 51

15  libdispatch.dylib             0x00007fff990c3467 _dispatch_client_callout + 28

16  libdispatch.dylib             0x00007fff990d6c1c _dispatch_main_queue_callback_4CF + 1685

17  com.apple.CoreFoundation       0x00007fff97ae9789 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9

18  com.apple.CoreFoundation       0x00007fff97aa873d __CFRunLoopRun + 1949

19  com.apple.CoreFoundation       0x00007fff97aa7d38 CFRunLoopRunSpecific + 296

20  com.apple.HIToolbox           0x00007fff99331d55 RunCurrentEventLoopInMode + 235

21  com.apple.HIToolbox           0x00007fff99331b8f ReceiveNextEventCommon + 432

22  com.apple.HIToolbox           0x00007fff993319cf _BlockUntilNextEventMatchingListInModeWithFilter + 71

23  com.apple.AppKit               0x00007fff869acf3a _DPSNextEvent + 1067

24  com.apple.AppKit               0x00007fff869ac369 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454

25  com.apple.AppKit               0x00007fff869a0ecc -[NSApplication run] + 682

26  com.apple.AppKit               0x00007fff8696a162 NSApplicationMain + 1176

27  com.vmware.fusion             0x000000010d0b499f 0x10d0a9000 + 47519

28  libdyld.dylib                 0x00007fff9513c5ad start + 1

Thread 0 crashed with X86 Thread State (64-bit):

  rax: 0x0000000000000000  rbx: 0x0000000000000006  rcx: 0x00007fff52b53918  rdx: 0x0000000000000000

  rdi: 0x0000000000000203  rsi: 0x0000000000000006  rbp: 0x00007fff52b53940  rsp: 0x00007fff52b53918

   r8: 0x00000000fffffffc   r9: 0x00007fff76eda9b8  r10: 0x0000000008000000  r11: 0x0000000000000206

  r12: 0x000000010e96a93a  r13: 0x00007fff52b54bd8  r14: 0x00007fff77c0d000  r15: 0x00007fff767d5070

  rip: 0x00007fff864d50ae  rfl: 0x0000000000000206  cr2: 0x000000010ea8aec0

Logical CPU:     0

Error Code:      0x02000148

Trap Number:     133

[MarkCarey]

I've had the same problem here.  It appears to be a glitch in the way that the Virtual Desktop decides how big to make the viewing area for a given full screen application.  Given the amount of work Apple's put in on this sub-system recently, I would suggest that it's likely a bug on the Apple side of the house.

There IS a workaround that seems to work for me.  If I get this kind of crash on launch of a VM, I simply:

1. show all virtual desktops,

2. then add one,

3. exit the selection screen to the Finder,

4. then show all desktops,

5. then remove the one I just added. 

6. Then I relaunch VMWare Fusion. 

Usually this solves the issue.  I suspect that Apple is getting bombarded with this bug, since it seems to be effecting any number of other applications that attempt to use their own render viewspaces for full screen drawing.  It'll likely get fixed shortly in an update. 

Good luck!

-M.

[davidh418]

I'm having the same problem. It went away after a couple of days, but since telling support to close the ticket, it's come back with a vengeance.

Given that I had Fusion 6 running on El Capitan just before the "upgrade" to 8.0.1, I would refute the suggestion that it's something on the Apple side. If the older version of Fusion can be stable, I see no reason to expect a later version to be any less so.

In my case, the instability started just after I allowed Fusion to upgrade my virtual machine. However, I had only used it once before that, so it may just be a coincidence.

Occasionally, it does stay up once Windows has started, but I haven't found a reliable way of getting it to stay up. From what I'm seeing, the instability seems to manifest itself when a mouse event happens over VMWare. I don't necessarily have to click on the window or the menu to make it crash; just move the mouse over it.

Anyway, to me this is unacceptable. As far as I am concerned, VMWare Fusion 8.0.1 is not fit for purpose, nor is it of merchantable quality. We should not accept this kind of regression in software that we have had to pay money for in order to obtain. It isn't as if we were able to try it out before parting with our cash.

[HagenV]

Same problem here.

First ran into this problem using VMware Fusion 7.x (latest version), so upgraded to Fusion 8.0.1. However the problem didn't disappear.

A work-around seems to be the following procedure:

• Start VMware fusion
• Switch to full screen mode using the "green button" (maximize window)
• Then startup the virtual machine

[hollyerp]

Same here, started happening a few days ago after upgrading to 10.11 then it 'seemed' to go away. Upgraded to 10.11.1 yesterday and now it's back this morning - can't start my Win 8 VM - which I need to have alongside OSX.

davidh418‌ It's perfectly possible for this to be on the Apple side. Just because V6 worked for you and V8 didn't, doesn't mean its definitely a problem with Fusion. If the problem is indeed related to Spaces, and the new split screen feature, then you are unlikely to see this bug in V6 because V6 does not attempt to use this OSX feature. However, version 8 does attempt to make use of this feature - so comparing V6 and V8 in this respect is akin to comparing apples and oranges.

The bug could be on the Fusion side - i.e. how Fusion hooks into the split screen feature.

The bug could be on the Apple side - i.e. the underlying code that handles the split screen feature.

One thing I will note, which points me to think it could be Fusion, is that Fusion is the only application that currently crashes on my MBP. However, that said, I've found 10.11 to buggy, and iOS9 even more so. I'm guessing we're in for a hell of a ride with Apple now they no longer have Steve Jobs at the helm - bloated with 'features' rather than simple to use.

The simplest fix for me was to simply unplug my additional monitor, start up Fusion, plug it in again, and move VM Ware over to it manually. The crash appears to be when Fusion attempts to start up in full screen mode on a second monitor.

Regards

Paul

[davidh418]

Yes, that's exactly what the problem is. I put in a technical support request, and someone had a look remotely at my system. He recommended that, before I shut down the VM, I switch it to Single Window mode and drag the window to the primary monitor. The next time OS X starts, it will fire up VMWare in Single Window mode on the main screen. Then I have to drag the window to the monitor where I've always had the VM running, and open it to Full Screen mode. This does seem to fix the issue.

And it is on the Fusion side. He said they are working on a fix, which they hope to be in the next patch in about a month's time.

VMWare should not be touting this version as being targeted at OS X El Capitan, if it has problems with the way in which that OS manages its screens. That's the sort of issue that needs to be right BEFORE the software is launched as being El Capitan-compatible, rather than as a patch afterwards.

[SteveBolton]

Happens on VMWare Fusion 7.1.3 as well.  I was using a second monitor at work with the VM on that monitor. 
At home I have one large monitor and keep the macbook closed.

[zhus]

A crash issue about using multi-monitors on OS X 10.11  have been fixed in Fusion 8.0.2.

Can you try it with Fusion 8.0.2?

[rtperna]

I have Fusion 8.0.2, El Capitan 10.11.1, and my Windows 8 VM blows up and doesn't even pretend to launch.  Sometimes after I reboot it will let me get back into it, but several times a week I have to battle to get the VM to even boot without crashing.  Very frustrating. 

[rtperna]

Some additional detail - when Fusion crashes upon opening the VM, the only way to fix it is to unplug my external monitor from the Macbook, reboot OSX, open up the Windows 8 VM, THEN after it's done booting I can plug my external monitor back in.