I see this all the time on multiple instances, since 10.0. At first I wondered if it was a symptom of a clustered setup, but we have since set up a separate non-clustered single server setup and it still does it.
I think it may also be linked to Self Service “timing out” all the time, ie. not refreshing, even with cmd +R. This seems more prevalent on some servers than others, but no idea why. At the moment we have to tell users to close and reopen the app whenever they want to use it (if it hasn’t already crashed if it’s own accord), which is obviously a poor experience.
At one time I had a support ticket in for this, but their advice was to change the policy timeout setting, which didn’t solve the problem but I didn’t have time to follow it up. I’ll try and reopen the ticket next week.
