We've thus far been unable to reproduce this failure internally. We do have a bug open to investigate, but it would help us greatly identify the culprit if someone who is afflicted could provide precise, reproducible instructions that our engineers could use to diagnose the problem.
Our Engineers have identified the issue and are working on the fix for the upcoming release.
Thank you for your patience.