Comment 2 for bug 1982608

Fair enough, I wasn't entirely clear. I've only been using 2.2.6 for a couple of weeks as I am testing whether it is stable enough to upgrade our production and development systems to. The error I reported has only happened once so far. If it happens again, I will of course update this bug description and do some more poking around at it.

We run sbcl 2.0.9 as our development and production setup and it gets a lot of use and we've never seen something like this. So while I agree it's possible this was a one off issue, my gut feel is it's a real problem.