During development this would sometimes break but only in very specific circumstances, and because they were so absurd and seemingly specific to our local development environment I just added an error message saying "watch and amaze while the application eats itself!" Or something to that effect. It was inspired by an error I saw with the Discworld game for the original PlayStation.
Of course, once this hit production it turns out the det of circumstances necessary to trigger this error wasn't quite as specific as I'd thought, and support was overloaded by hundreds of people calling in to report the error, worried that their money was gone. Of course, people using these feature were high rollers placing very large bets, so management was not happy...
Fortunately I wasn't fired and we fixed the issue very quickly, but man I felt the edge of that sword really close to my neck. It was at one of my first jobs as well nearby 20 years ago. I definitely learned some valuable lessons that week. :o)