Comment 3 for bug 1361935

> This must be something else, given the fact that the timestamps are same.

Isn't this just because two processes get started simultaneously?

And one of these processes then finds that the state needs not to get changed (after waiting for the lock).