Spent ages tracking down a weird not-actually-crashing bug. Turns out it was the framework I'm using getting recursively confused and taking about five minutes, with its memory usage growing to about 150MB, to return an error message. It took a couple of hours for me to actually wait five minutes and see the message, rather than killing the process (because I assumed it was in an infinite loop) and trying to work out where the problem had been introduced with git bisect, which involved loads of rolling back database migrations and other such shenanigans
Once I saw the message, it was quite straightforward to fix
I'm now going to get a beer and watch Capricorn One
Once I saw the message, it was quite straightforward to fix
I'm now going to get a beer and watch Capricorn One
Comment