Thanks @yaypie, you're right; as soon as I updated Chrome the problem disappeared. Thanks.