It looks like a bug in Chrome. We can't fix issues like that, you should report them to Google.
However, VMs can sometimes cause issues like this - have you tried running Chrome in the host OS rather than in a VM? If you cannot reproduce the problem in the host OS it could well be a bug in the VM, in which case it's neither Google's nor our fault. I wouldn't recommend running a browser in a VM anyway, since the performance is likely to be very poor.