Despite the fact that this bug seems to be exceedingly rare, we have taken the same approach to it that we do with all reported technical issues - we try to recreate it and determine the root cause. We have not been able to recreate it internally, which tells us that it's likely to be related to the user's environment in some way (cached cookies, etc.). We are continuing to investigate and working to get it resolved.