So far you and I believe two other users total have been able to reproduce this problem. We were only able to debug it and find a fix by calling one of those users on the phone and doing a screen share and investigating on thier machine.
We have tried repeatedly to reproduce the error even after it was reported and we are still unable to. We still don't know any simple test scenario that causes this problem. We are lucky enough to report we have a workaround for now and a fix coming in a future update.