After four days uptime my MacBook running Tiger with the latest available updates started to behave oddly. Every program I tried to launch refused to start up. The corresponding program icon in the Dock just kept bouncing and after a while it stopped and i had to kill it (force quit).
I can't recall if I was doing anything extraordinary. At least Safari, aMule, iTerm and Smultron were open. I was just starting Transmission (a BitTorrent client) when the problem first occurred, i.e. Transmission wouldn't start. And as I said, I couldn't launch any program after that. All running programs were fine.
/var/log/system.log says the window server crashed repeatedly. And I got an other error message too. See below. (Sorry about the duplicate messages, basically there are just two different error messages)
So any ideas what happened? What do those fs-events lines mean?
I can't recall if I was doing anything extraordinary. At least Safari, aMule, iTerm and Smultron were open. I was just starting Transmission (a BitTorrent client) when the problem first occurred, i.e. Transmission wouldn't start. And as I said, I couldn't launch any program after that. All running programs were fine.
/var/log/system.log says the window server crashed repeatedly. And I got an other error message too. See below. (Sorry about the duplicate messages, basically there are just two different error messages)
Code:
[COLOR="DarkGreen"]Jun 20 21:30:50 localhost crashdump[1067]: WindowServer crashed
Jun 20 21:30:51 localhost crashdump[1067]: crash report written to: /Library/Logs/CrashReporter/WindowServer.crash.log
Jun 20 21:33:14 localhost crashdump[1070]: WindowServer crashed
Jun 20 21:33:14 localhost crashdump[1070]: crash report written to: /Library/Logs/CrashReporter/WindowServer.crash.log
Jun 20 21:35:28 localhost crashdump[1095]: WindowServer crashed
Jun 20 21:35:28 localhost crashdump[1095]: crash report written to: /Library/Logs/CrashReporter/WindowServer.crash.log
Jun 20 21:35:46 localhost crashdump[1097]: WindowServer crashed
Jun 20 21:35:46 localhost crashdump[1097]: crash report written to: /Library/Logs/CrashReporter/WindowServer.crash.log
Jun 20 21:37:20 localhost crashdump[1102]: WindowServer crashed
Jun 20 21:37:20 localhost crashdump[1102]: crash report written to: /Library/Logs/CrashReporter/WindowServer.crash.log
Jun 20 21:39:40 localhost crashdump[1105]: WindowServer crashed
Jun 20 21:39:41 localhost crashdump[1105]: crash report written to: /Library/Logs/CrashReporter/WindowServer.crash.log[/COLOR]
[COLOR="DarkRed"]Jun 20 21:40:05 localhost kernel[0]: fs_events: add_event: event queue is full! dropping events.
Jun 20 21:40:05 localhost kernel[0]: fs_events: add_event: event queue is full! dropping events.
Jun 20 21:40:05 localhost kernel[0]: fs_events: add_event: event queue is full! dropping events.
Jun 20 21:40:05 localhost kernel[0]: fs_events: add_event: event queue is full! dropping events.
Jun 20 21:40:05 localhost kernel[0]: fs_events: add_event: event queue is full! dropping events.
Jun 20 21:40:05 localhost kernel[0]: fs_events: add_event: event queue is full! dropping events.
Jun 20 21:40:06 localhost kernel[0]: fs_events: add_event: event queue is full! dropping events.
Jun 20 21:40:06 localhost kernel[0]: fs_events: add_event: event queue is full! dropping events.
Jun 20 21:40:07 localhost kernel[0]: fs_events: add_event: event queue is full! dropping events.
Jun 20 21:40:07 localhost kernel[0]: fs_events: add_event: event queue is full! dropping events.[/COLOR]
[COLOR="DarkGreen"]Jun 20 21:40:11 localhost crashdump[1108]: WindowServer crashed
Jun 20 21:40:12 localhost crashdump[1108]: crash report written to: /Library/Logs/CrashReporter/WindowServer.crash.log
Jun 20 21:40:24 localhost crashdump[1110]: WindowServer crashed
Jun 20 21:40:25 localhost crashdump[1110]: crash report written to: /Library/Logs/CrashReporter/WindowServer.crash.log[/COLOR]So any ideas what happened? What do those fs-events lines mean?
