It's a bug Apple introduced in 10.14.6 that Apple are working on, plus Apple changed it's memory management in a minor update that has affected the way memory is managed in macOS. Apple has acknowledged the bug and VMware released 11.1.1 as a fix. However the memory management change in macOS means much more work for VMware to address what has happened, and I suspect other software vendors.
Apple has done this before changing something between the last beta version and the gold master which is released. That's possibly why VMware may have been caught out.
I am using 10.14.1 on a MacBook Pro 15" 2018 model, MacBookPro15,1.
Can you check to see if there are .vmem files being created in the VM folder please? If so the config changes have not been applied properly.