Well, after a day the bug is back, so xserver update didn't help. @Clément Guérin - I have this bug on default Chrome, turning on HW just makes it more frequent.