We’ve found a reliable way to reproduce the issue and have implemented a fix. This will roll out in a future update.