noogle
Contributor
Contributor

VMware Fusion Start Menu assertion failed, 4 per second in System log

Jump to solution

I keep seeing this message in the system log, at a rate of 4 lines per second...

Example:

29/10/2014 07:23:24.233 VMware Fusion Start Menu[5573]: assertion failed: 14A389: libxpc.dylib + 40320 [9437C02E-A07B-38C8-91CB-299FAA63083D]: 0x13

Running 7.0.1, also seen on 7.

Fusion is not running.

It makes checking the log files for other information quite difficult.

Anyone else see this, or know the cause / resolution ?

1 Solution

Accepted Solutions
eltjo
Contributor
Contributor

I had the same issue, but after I performed the VMware Free upgrade the issue was resolved.

View solution in original post

0 Kudos
12 Replies
kccarlton
Contributor
Contributor

I'm seeing this as well. Was a big surprise when I checked the log for something else. I wondered by Clean My Mac was struggling with the logs since I am not currently developing anything. Now I know. This is a huge issue. Not happy and I've loaded a ton of apps in my VM. Grrr. We just need to know if it is config issue (PATH, etc) or something the user (us) can fix. Otherwise, VM - please get on this.

iMac 2009, OS X Yosemite, Fusion 6

0 Kudos
pinney_colton
Contributor
Contributor

Agreed - same issue here.  Killing the the VMWare Fusion Start Menu.app process at the command line stops the log messages, but I suspect they will resume the next time I launch and/or shutdown a VM and exit Fusion (6.0.4).

0 Kudos
SteveBolton
Contributor
Contributor

I see this on Yosemite with Fusion 7.

The finder has been hanging for long periods today - when I killed the Start Menu process the Finder responded immediately.

Using a Retina MacBook Pro, late 2013, 2GHz Core I7, 16GB 1600Mhz DDR3, Iris Pro 1536MB

0 Kudos
mihaval
Contributor
Contributor

Also seeing this on iMac, OS X 10.10, but not on Macbook Air, OSX 10.10. Filing support request

0 Kudos
mdavids
Contributor
Contributor

Same here.

$ sw_vers

ProductName: Mac OS X

ProductVersion: 10.10

BuildVersion: 14A389


VMware Fusion

Professional Version 7.0.0 (2103067)


0 Kudos
mihaval
Contributor
Contributor

Hi!

I contacted support about that. The guidance was to change the virtual machine settings (go to virtual machine -> settings -> Application Menu -> Show only when machine is running.

In my case, I killed the process "/Applications/VMware Fusion.app/Contents/Library/VMware Fusion Start Menu.app/Contents/MacOS/VMware Fusion Start Menu -psn_0_303178" and the messages stopped. Even when I relaunched VMware Fusion (and the process was started again), the messages did not reappear in console.

I even rebooted the host OSX machine and the messages are still not appearing in the log file. It seems that there was something "stuck" in the "VMware Fusion Start Menu" process. Now, it does not make a difference to what setting i put the "Application menu" in virtual machine setting.

hth,

Miha.

lailoken
Contributor
Contributor

Same here. I also did not have any VM running at the time.

0 Kudos
Bob47
Contributor
Contributor

I just discovered the same problem.  Yosemite 10.10 running Fusion 7.0.1 on mid-2012 MacBook Pro with 16GB RAM, 15" Retina, 256GB SSD.  System log screen shot attached.  No error messages in the VMware Fusion Start Menu log.

0 Kudos
eltjo
Contributor
Contributor

I had the same issue, but after I performed the VMware Free upgrade the issue was resolved.

View solution in original post

0 Kudos
HPReg
VMware Employee
VMware Employee

So just to clarify, is anybody still seeing this issue in Fusion 7.1? If not, can the original poster mark this question as "Answered"? Thanks!

0 Kudos
noogle
Contributor
Contributor

Apologies - I forgot to follow this up. Have marked as answered since the problem has gone with the latest updates.

Thanks.

0 Kudos
lailoken
Contributor
Contributor

Seems to be solved for me as well.

0 Kudos