This must be caused by the updated chrome. We haven't changed anything else regarding this.

Anyway... It looks like this for me in 4.6.0. Isn't that expected?