Skip to content
{ 2003 07 25 }

Cripes! WindowServer just crashed

Sheesh. The WindowServer just bit the dust on my PowerBook. That was the weirdest experience. I wonder how many other people have watched their WindowServer die on them. First, I’m typing then I see the little swirling circle at the bottom of the screen as if the computer is about to reboot. Then the screen goes blue and then I’m watching as the Desktop slowly rebuilds itself sans all of my running apps. Wonderful. Then again I’ve had similar situations with Windows doing the exact same thing when Explorer just dies and needs to be kickstarted back to life.

For the geek inclined here is a log courtesy of /var/log/system.log:

Jul 25 11:43:39 basho crashdump: Crash report written to: /Users//Library/Logs/CrashReporter/WindowServer.crash.log
Jul 25 11:43:39 basho WindowServer[167]: Received fatal signal (11) at PC 0x90004288; exiting
Jul 25 11:43:39 basho mach_kernel: IOHIDSystem: doKickEventConsumer msg_send returned 268435459
Jul 25 11:43:39 basho /usr/libexec/crashreporterd: task_set_exception_ports() failed: (os/kern) invalid argument
Jul 25 11:43:42 basho crashdump: Crash report written to: /Library/Logs/CrashReporter/???.crash.log
Jul 25 11:43:42 basho /usr/libexec/crashreporterd: exception_raise() failed forwarding exception: (os/kern) invalid argument
Jul 25 11:43:42 basho /usr/libexec/crashreporterd: newport: 2803 originalport: b07 thread: ffffffff task: a1b exception: 1
Jul 25 11:43:42 basho /usr/libexec/crashreporterd: mach_msg() reply failed: (ipc/send) invalid destination port
Jul 25 11:43:42 basho /usr/libexec/crashreporterd: task_set_exception_ports() failed: (ipc/send) invalid destination port
Jul 25 11:43:43 basho crashdump: Crash report written to: /Library/Logs/CrashReporter/???.crash.log
Jul 25 11:43:43 basho /usr/libexec/crashreporterd: exception_raise() failed forwarding exception: (os/kern) invalid argument
Jul 25 11:43:43 basho /usr/libexec/crashreporterd: newport: 2803 originalport: b07 thread: ffffffff task: ffffffff exception: 1
Jul 25 11:43:43 basho /usr/libexec/crashreporterd: mach_msg() reply failed: (ipc/send) invalid destination port
Jul 25 11:43:43 basho /usr/libexec/crashreporterd: task_set_exception_ports() failed: (ipc/send) invalid destination port
Jul 25 11:43:44 basho crashdump: Crash report written to: /Library/Logs/CrashReporter/???.crash.log

Be Sociable, Share!
Posted by hoanga on Friday, July 25, 2003, at 1:43 pm. Filed under osx. Follow any responses to this post with its comments RSS feed. Both comments and trackbacks are currently closed.

{ 2 } Comments

  1. Dave | October 23, 2003 at 12:21 pm | Permalink

    Interesting. I have had far too many crashes with my new 12″ PowerBook running 10.2.8. I just had the same crash that you did:

    Oct 23 11:06:58 mojobook mach_kernel: IOHIDSystem: doKickEventConsumer msg_send returned 268435459
    Oct 23 11:06:58 mojobook WindowServer[188]: Received fatal signal (11) at PC 0x9370f21c; exiting
    Oct 23 11:06:58 mojobook loginwindow[416]: MIG: server died : CGSExtractEventRecordsFromMessage
    Oct 23 11:06:59 mojobook loginwindow[416]: kCGErrorInvalidConnection : CGSRemoveHotKey: Invalid connection
    Oct 23 11:06:59 mojobook last message repeated 3 times

    I’ve had kernel panics, a corrupted boot volume, and other happy events. FYI, here’s what I’m runnning:

    FruitMenu 3.1
    LiteSwitch X 1.5.1
    Silk 1.1
    USB Overdrive 10.2.2
    APE 1.3
    Timbuktu Pro 6.02
    Retrospect Client 5.044

    I’d be interested to know if there are any correlations in our setups. I’m close to sending the whole kit back to Apple for a replacement.

    Dave

  2. Mortgage Loan | March 21, 2006 at 5:06 pm | Permalink

    Your site is very informational for me. Nice work.