[Issue] VMware Fusion 11.5.2 shuts down agents randomly on macOS Catalina 10.15.3

[WTruitt]

The errors reported and scrapped logs are below. E105 is the first error reported in the given time period.

2020-04-25T11:32:50.643-06:00| worker-7235712| E105: PANIC: MXUserWaitInternal: failure 22 on condVar (0x7FAEA783BA70; workerLibLock)

2020-04-25T11:32:50.643-06:00| worker-7235712| I125: Panic: can't get userlevel lock.

2020-04-25T11:32:50.643-06:00| worker-7235712| W115:

2020-04-25T11:32:50.643-06:00| worker-7235712| W115+ The core dump limit is set to ZERO; no core dump should be expected

2020-04-25T11:32:50.643-06:00| worker-7235712| I125: Backtrace:

2020-04-25T11:32:50.644-06:00| worker-7235712| I125: Backtrace[0] 0000700003272a00 rip=000000010c1bdbcb rbx=0000000000000000 rbp=0000700003272ee0 r12=0000000000000001 r13=0000000000000000 r14=000000010d0418a8 r15=0000000000000016

..

..

..

2020-04-25T11:32:50.650-06:00| worker-7235712| I125: [113B66000-113CC3000): /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio

2020-04-25T11:32:50.650-06:00| worker-7235712| I125: [7FFF4B745000-7FFF4B797000): /System/Library/PrivateFrameworks/AudioSession.framework/Versions/A/AudioSession

2020-04-25T11:32:50.650-06:00| worker-7235712| I125: [7FFF4B797000-7FFF4B7C5000): /System/Library/PrivateFrameworks/AudioSession.framework/libSessionUtility.dylib

2020-04-25T11:32:50.650-06:00| worker-7235712| I125: End printing loaded objects

2020-04-25T11:32:50.650-06:00| worker-7235712| I125: Writing monitor `vmmcores.gz`

2020-04-25T11:32:50.659-06:00| worker-7235712| W115: Dumping core for vcpu-0

2020-04-25T11:32:50.659-06:00| worker-7235712| I125: Beginning monitor coredump

2020-04-25T11:32:50.746-06:00| mks| W115: Panic in progress... ungrabbing

2020-04-25T11:32:50.746-06:00| mks| I125: MKS: Release starting (Panic)

2020-04-25T11:32:50.746-06:00| mks| I125: MKS: Release finished (Panic)

2020-04-25T11:32:50.779-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1c (0) Bad address

2020-04-25T11:32:50.779-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1d (0) Bad address

2020-04-25T11:32:50.779-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1e (0) Bad address

2020-04-25T11:32:50.779-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1f (0) Bad address

2020-04-25T11:32:51.034-06:00| worker-7235712| I125: End monitor coredump

2020-04-25T11:32:51.034-06:00| worker-7235712| W115: Dumping core for vcpu-1

2020-04-25T11:32:51.034-06:00| worker-7235712| I125: Beginning monitor coredump

2020-04-25T11:32:51.145-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1c (0) Bad address

2020-04-25T11:32:51.145-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1d (0) Bad address

2020-04-25T11:32:51.145-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1e (0) Bad address

2020-04-25T11:32:51.145-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1f (0) Bad address

2020-04-25T11:32:51.399-06:00| worker-7235712| I125: End monitor coredump

2020-04-25T11:32:51.399-06:00| worker-7235712| W115: Dumping core for vcpu-2

2020-04-25T11:32:51.399-06:00| worker-7235712| I125: Beginning monitor coredump

2020-04-25T11:32:51.504-06:00| worker-7235712| I125: CoreDump error: Read, page 0xc33 (0x784660) Bad address

2020-04-25T11:32:51.511-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1c (0) Bad address

2020-04-25T11:32:51.511-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1d (0) Bad address

2020-04-25T11:32:51.511-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1e (0) Bad address

2020-04-25T11:32:51.511-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1f (0) Bad address

2020-04-25T11:32:51.765-06:00| worker-7235712| I125: End monitor coredump

2020-04-25T11:32:51.765-06:00| worker-7235712| W115: Dumping core for vcpu-3

2020-04-25T11:32:51.765-06:00| worker-7235712| I125: Beginning monitor coredump

2020-04-25T11:32:51.870-06:00| worker-7235712| I125: CoreDump error: Read, page 0xc33 (0x245777) Bad address

2020-04-25T11:32:51.878-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1c (0) Bad address

2020-04-25T11:32:51.878-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1d (0) Bad address

2020-04-25T11:32:51.878-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1e (0) Bad address

2020-04-25T11:32:51.878-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1f (0) Bad address

2020-04-25T11:32:52.133-06:00| worker-7235712| I125: End monitor coredump

2020-04-25T11:32:52.133-06:00| worker-7235712| W115: Dumping core for vcpu-4

2020-04-25T11:32:52.133-06:00| worker-7235712| I125: Beginning monitor coredump

2020-04-25T11:32:52.245-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1c (0) Bad address

2020-04-25T11:32:52.245-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1d (0) Bad address

2020-04-25T11:32:52.245-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1e (0) Bad address

2020-04-25T11:32:52.245-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1f (0) Bad address

2020-04-25T11:32:52.499-06:00| worker-7235712| I125: End monitor coredump

2020-04-25T11:32:52.499-06:00| worker-7235712| W115: Dumping core for vcpu-5

2020-04-25T11:32:52.499-06:00| worker-7235712| I125: Beginning monitor coredump

2020-04-25T11:32:52.603-06:00| worker-7235712| I125: CoreDump error: Read, page 0xc33 (0x5ae3c2) Bad address

2020-04-25T11:32:52.611-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1c (0) Bad address

2020-04-25T11:32:52.611-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1d (0) Bad address

2020-04-25T11:32:52.611-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1e (0) Bad address

2020-04-25T11:32:52.611-06:00| worker-7235712| I125: CoreDump error: Read, page 0xd1f (0) Bad address

2020-04-25T11:32:52.865-06:00| worker-7235712| I125: End monitor coredump

2020-04-25T11:32:56.796-06:00| worker-7235712| I125: Exiting

A little research tells me that the error is thrown at #L312 of this function open-vm-tools/ulCondVar.c at master · vmware/open-vm-tools · GitHub

But, I can't find the root cause of thy this is happening. The previous instance of this issue occurred on April 14 so this is becoming more regular in its occurrence.

[Setheck]

So i last posted over 2 months ago, this is still happening, I have gotten very little help from my support case and not even a 'quick' response here. 

@dariusd @nancyz @Mikero 

Any suggestions on how I can get some assistance? So far the community and official support channel (service request) has not gone anywhere close to even providing me information to do my own investigation.

I have probably sent 20 crash reports and supposedly my support case was escalated to the 'Engineering Team' but that was on 4/8 and I have had no follow up since then. The canned email that comes back from updating a support request really needs the `no later than one business day.` removed.

[Mikero]

Does the issue persist with Fusion 12 (Player, which is free...)?

Fusion 11 is out of support and EOL, I don't expect engineering to look at bugs on this branch.

[Setheck]

I will look into Fusion 12, but why is doesn't the official support team know that 11 is EOL? Instead they just ignore me? I am beyond frustrated.

[Gonzalo2]

We are having the same issue, now with Monterey 12.4 in the host, VMWare Fusion 12.2.3 and Bigsur in the guests.