That sounds like this bug re retina screens:
but that shouldn’t be affecting you if you are using v 1.90.3?