5 ms·
It's a race condition, so it had to do with two operations happening in a certain incorrect order. I bet they are able to see the exact situations where it occu
by lambda_obrien 6y ago
It's a race condition, so it had to do with two operations happening in a certain incorrect order. I bet they are able to see the exact situations where it occurred with pretty great certainty by reviewing the logs of the two operations that raced and see where the incorrect operation won. They even say they are invalidating all sessions or of an abundance of caution, indicative that they are pretty sure about it.
- IncRnd 6y agoYou called it! Just another race condition that uses shared objects without protecting them.