Believe it or don't, this is actually a manifestation of the bug that was reported here.

As stated in our reply, the issue has been addressed and should be reflected in patch 1.22a.

Thanks again for the post!