@craigtheatheist Hard to know for sure, but I bet I've had more full system "crashes" in 2012 than in all prior years of Mac OS X combined.
@craigtheatheist Seems to be a widespread issue for people since 10.7.x. You'd think this sort of thing would be a high priority.
@craigtheatheist Just Apple ones. It's happened with Message, Flurry, and Arabesque.
@c_had It's been happening on and off since Lion. Both 2010 MBP and Retina MBP.
@craigtheatheist A bunch of WindowServer errors and complaints that ScreenSaverEngine is using deprecated NSImage methods.
And I should have used osascript to tell NetNewsWire to quit so that it wouldn't lose all my read statuses.
@rentzsch That was my plan if it hadn't panicked. I'll try that first next time unless someone knows how to unlock the screen via ssh.
@craigtheatheist Killing the screensaver process just gave me a blue screen. And then shortly after it kernel panicked.
Another freeze at the screensaver. Could ssh in but to do what? Now trying just energy saver and screen lock, no screensaver.