I've just spoken with our QA team, and they are going to look into this later today.
If all goes well, the issue will be fixed by 1.22c.

Thanks for the report!