I really like good debugging stories; written well, they're like a very short mystery story, in which I get to follow the thought process and watch the bug bein

I really like good debugging stories; written well, they're like a very short mystery story, in which I get to follow the thought process and watch the bug being cornered and identified, and ultimately it goes in my personal arsenal of things to think about in the future if I'm ever in a similar situation. Sadly, this one is ruined by having the answer stuck in the first paragraph with a great big "TL;DR" in it, so even if I read the whole thing now, I already know the answer which colours my thinking the whole way through. What a disappointment. It's even got the word "story" in the title.