Ah, darn. I've gotten one other report of this happening, it seems to be an invalid memory access in a GL bug.
