In order to prevent this from happening I figured out that you can change the the value of the /proc/[id_of_vmware_vmx_process]/oom_adj to -17. I have made a small shell script that checks whether the vmware process is running and if this is the case, adjust the oom_adj value:
contents of /usr/bin/vmware-protect-from-oom.sh:
#!/bin/bash
pid=$(pidof vmware-vmx)
if [ $pid > 0 ]; then
sudo echo "-17" > /proc/$pid/oom_adj
fi
sudo crontab -e
):* * * * * /usr/bin/vmware-protect-from-oom.sh