This is a known problem with systems where the display scaling is not 100%.
Also reported here:
With a work-around: