![]() When I force quit Mail and, things run smoothly, so the problem seems to be limited to the Mail application. I have no firewall app running and have looked into my log file which is available here: Two or three times, I even got a complete freeze, the cursor not moving anymore, the fans (which were running constantly before) shut down the only thing I could do was holding the power button for five seconds. The Mail application doesn't show any window during maybe the first hour after trying to open it, and once I see the main window, everything is so slow that even opening an e-mail can - if it works at all - take a loooot of time. The activity monitor shows that "Mail" and "" both have 90%+ under "% CPU", and most of the time Mail is "Not Responding". When Mail is running, everything slows down extremely (I constantly see beach balls and spend most of the time waiting for any of my inputs showing an effect, not just in Mail but with everything). Output parameters from ASL Module "" override any specified in ASL Module "".ĪSL Module "" claims selected messages.ĪSL Module "" claims selected messages.ĪSL Module "" claims selected messages.ĪSL Module "" claims selected messages.ĪSL Module "" claims selected messages.ĪSL Module "" claims selected messages.ĪSL Module "" claims selected messages.ĪSL Module "" claims selected messages.ĪSL Module "" claims selected messages.ġ2/22/13 9:32:54.000 AM kernel: Longterm timer threshold: 1000 msġ2/22/13 9:32:54.000 AM kernel: Darwin Kernel Version 13.0.0: Thu Sep 19 22:22: root:xnu-2422.1.Since I updated to Mavericks two days ago on my late 2008 13-inch MacBook (first unibody aluminium), I have huge difficulties using Mail. Those messages may not appear in standard system log files or in the ASL database.ĪSL Module "" sharing output destination "/var/log/system.log" with ASL Module "". Note the three minutes from BOOT_TIME to the first Configuration Notice:ġ2/22/13 9:29:42.000 AM bootlog: BOOT_TIME 1387722582 0ġ2/22/13 9:32:54.000 AM syslogd: Configuration Notice:ĪSL Module "" claims selected messages. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.) Please don’t post any other kind of diagnostic report, such as hang logs - they're very long and not helpful. Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the entire contents of the most recent one, if any. Important: Some private information, such as your name, may appear in the log. Please do not indiscriminately dump thousands of lines from the log into this discussion. In most cases, a few dozen lines are more than enough. When posting a log extract, be selective. Don’t post many repetitions of the same message. If there are runs of repeated messages, post only one example of each. Please include the BOOT_TIME message at the beginning of the log extract. Paste into a reply to this message ( command-V).įor example, if the problem is a slow startup taking three minutes, post the messages timestamped within three minutes after the boot time, not before. Copy them to the Clipboard by pressing the key combination command-C. ![]() Select the messages logged after the boot, during the time something abnormal was happening. Now clear the search box and scroll back in the log to the last boot time when you had the problem. Note the timestamps of those log messages, which refer to the times when the system was booted. If you don't see that menu, selectĮnter "BOOT_TIME" (without the quotes) in the search box. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. Make sure the title of the Console window is All Messages. ![]() Click Utilities, then Console in the icon grid. The application is in the folder that opens. ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. Select it in the results (it should be at the top.) ☞ Enter the first few letters of its name into a Spotlight search. Launch the Console application in any of the following ways: ![]() If you have more than one user account, these instructions must be carried out as an administrator.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |