The below is an off-site archive of all tweets posted by @mjtsai ever

October 8th, 2012

@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.

via Twitterrific for Mac in reply to craigtheatheist

@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.

via Twitterrific for Mac in reply to craigtheatheist

@craigtheatheist Just Apple ones. It's happened with Message, Flurry, and Arabesque.

via Twitterrific for Mac in reply to craigtheatheist

@c_had It's been happening on and off since Lion. Both 2010 MBP and Retina MBP.

via Twitterrific for Mac in reply to c_had

@craigtheatheist A bunch of WindowServer errors and complaints that ScreenSaverEngine is using deprecated NSImage methods.

via Twitterrific for Mac in reply to craigtheatheist

And I should have used osascript to tell NetNewsWire to quit so that it wouldn't lose all my read statuses.

via Twitterrific for Mac

@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.

via Twitterrific for Mac in reply to rentzsch

@craigtheatheist Killing the screensaver process just gave me a blue screen. And then shortly after it kernel panicked.

via Twitterrific for Mac in reply to craigtheatheist

Another freeze at the screensaver. Could ssh in but to do what? Now trying just energy saver and screen lock, no screensaver.

via Twitterrific for Mac