We have a fix for this internally and are working on getting it into a hotfix. Thanks for the report!