It is so hard to remember exactly what one does when interacting with a program.
When I was developing a program to run a laboratory instrument, I had the amazing luck to work with a lab analyst who:
A. didn't own or like computers
and
B. Has an amazing memory, kind of like Sheldon on Big Bang. Sort of an antisocial type like him, too.
I hated this guy when I first met him, but over a few years, we became good friends, and he became a computer nut!
Anyhow, he had the amazing, and unusual ability to remember each step of whatever he did leading up to a crash or less-than-friendly behavior of my program.
One time, he said that what lead up to a particular failure was clicking both the right and left mouse buttons after performing a specific sequence of steps. NOBODY else in the world, including myself, could have remembered the sequence of events that created this crash.
He was the perfect test subject and co-developer of this software because of his hatred and distrust of computers, and his amazing memory and, also his lack of social skills. He was absolutely not afraid of hurting anyone's feelings, and this extended to mine when something about the program sucked!
He just told me flat out that it sucked! And that was so incredibly helpful! Anyhow, this recognition of the symptom and cause of this by
@srglassw reminds me of this.
That program and hardware is one of the projects of which I still am the most proud. And I owe so much of the credit to this guy, who was forced to work with me on its development.
He's still a good friend. This reminds me that I need to go visit him. He's a neat guy to those that bother to get past his gruff, unsocial exterior. He pushes people away initially, but would give you the shirt off his back to help you if you needed it.
Sorry for the off topic rant, but seeing how your events were recognized reminds me of this guy, with the uncanny ability to remember the specific steps leading to a problem in a program.