7 comments

[ 2.7 ms ] story [ 26.4 ms ] thread
Funny: the error message says "integer divide by 0", so it's basically stack overflow error.
(comment deleted)
Since when does a divide by zero error push too many items onto the stack?
The last time I remember SO being down, it was because someone entered a unhealthy amount of whitespace somewhere. I'm curios what caused it this time.

Aaaaand it up again for me.

Cause was our primary SQL server BugChecked :-( Doing a full internal write up now, and expediting a SQL maintenance window for tomorrow so we can run some memory checks on the system that crashed.
It seems to be up right now in "read only mode"

That is probably a good lesson for incident response... have a plan to get a subset of your functionality that services most of your users up and running quickly and then bring up the more complex stuff that is less commonly used.

(comment deleted)