Did that error go away? I'm getting the same error report, and I've seen it happen.