We definitely weren't aware of this bug & haven't been able to reproduce it yet. There are several engineers looking into what could cause the problem right now, and I hope we'll be able to give you some feedback soon.