Comment 19 for bug 504291

In theory, if something screwed up previously in the request this bad there should be an OOPS and this will be the second (or third) OOPS being generated for that request. An OOPS could have a pointer to the previous OOPS generated by that thread. We might not even want to reset this between requests for those cases like this one where bad state might have been caused by a previous request.