It seems to be a known Chrome bug that only affects Macs without retina screens https://bugs.chromium.org/p/chromium/issues/detail?id=596223 The odd thing is: this didn't affect the previous version as badly for some reason. Won't fix (can't fix?) - even if we had a technical solution for this it's probably not worth it for many reasons.