I was able to reproduce this. Thanks for the report.

We believe we've fixed this in our previous update. If you're still seeing this, please submit a new bug report, and we'll look into it ASAP!