Hi, Chrisnorth.
Angus is correct in that the WindowServer process crashed, but this generally won't permit you to send a report to Apple, and Apple does not respond to the reports you send.
I suggest the following:
1. Since this is happening with browsers, clear the browser cache files. In Safari this is Command-E. I suspect there is a similar option in FireFox.
2. As a general check, run the procedure specified in my
Resolving Disk, Permission, and Cache Corruption FAQ. Perform the steps therein in the order specified.
3. If you have personal Web space, post related crash logs to such and post a link to these in a reply here. Crash logs reside in one of two folders:
(1) Home > Library > Logs > CrashReporter -- contains crash logs for applications running under your Id. Each log is a file beginning with the name of the application, for example:
application_name.crash.log
All crashes for a specific application are in its log. Example: Mail.crash.log would contain
all the crash logs from crashes in the Mail application.
(2) Computer > Macintosh HD > Library > Logs > CrashReporter -- contains system-related crash logs. Like the application logs, each log is related to a specific kind of crash and contains all the crashes of that type. Example: fix_prebinding.crash.log
If you want to post information from a crash log, copy and paste
the most recent crash from within the log file. New crash logs are added to the end of the log file. A crash log begins with a date and time stamp like the following:
**********
Date/Time: 2003-03-11 13:19:52 -0600
where the Date/Time: stamp will indicate the date and time of the crash.
4. Look back through prior console.log files and system.log files to see any clues were left from the crash. Your Mac creates new console.log and system.log files at startup, when you restart, or when the logs are rotated by the daily CRON script. The daily CRON script can be executed manually or, if the Mac is powered-on and not in sleep mode overnight, at roughly 03:15 local time when the script is run automatically.
If you display the Logs pane in Console (click the Logs tool in the Console toolbar), in addition to looking at the current console.log and system.log files, you can look back through
- prior console.log files by selecting the disclosure triangle for /Library/Logs > Console > your Id in the left pane;
- prior system.log files by selecting the disclosure triangle for /var/logs in the left pane,
Prior console.logfiles are saved in files with file names console.log.
n where
n is an integer from 0-9. The higher the number, the older the log. For example:
- The console.log.0 file is the console.log log from the period immediately prior to the current console.log file.
- The console.log.1 file is from the the period immediately prior console.log.0 log, etc.
Prior system.log files are saved in files with file names system.log.
n.log.gz, where
n is an integer from 0-7. Once again, the higher the number, the older the log. For example:
- The system.log.0.log.gz file is the system.log log from the period immediately prior to the current system.log file.
- The system.log.1.log.gz file is from the the period immediately prior system.log.0.log.gz log, etc.
Note that some of the information above is from the Console and Crash Logs chapter of my book,
Troubleshooting MacŪ OS X.
Top
