MBP Freezing Up

Question

Level 1

8 points

MBP Freezing Up

Hi, I have a 2009 13 inch MBP with 4G of RAM. Its loaded with the current version of Snow Leopard, version 5.1.5 of Safari and version 4.5 0f the Mail App.

The screen of the MBP freezes up 3 - 4 times per day. Ninety percent of the time Safari is open when this happens (some of the time, the Mail App is open as well. The remainder of the time I may have another browser open, but the Mail app is open.

I can move the cursor around the screen and "force quit" any open applications except Mail and Safari when this happens. The icons for Safari and the Mail App in my Dock turn grey if I click on them. Otherwise the spinning pizza wheel shows up. I have to use the power button to turn off and restart the machine.

I have tried resetting the PRAM. I also got a couple of error messages concerning Hazel (v3.1.1) via Growl on one occasion. Simply stated that there was an error when Hazel started to run, checking .docx files for Music and video. (Hazel runs from startup and I have rules set up to remove partial and duplicate downloads and clear all Trash files within a set period). I uninstalled Hazel, but the freezing still occurs.

The apps I have running most of the day are Mail, a browser, Omnifocus, Preview and either Pages or Word in Office for Mac 2011. I back up a couple of times a day using Time Machine and every couple of days update a copy of my hard drive using Carbon Copy Cloner.

Anyone else having these problems, or able to suggest a solution?

Cheers

kevofoz.

MacBook Pro, Mac OS X (10.6.8), Safari (5.1.5) Mail (4.5)

Posted on May 10, 2012 12:23 AM

Reply

Answer 1

Linc Davis

Level 10

209,547 points

May 10, 2012 6:38 AM in response to kevofoz

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ If you’re running Mac OS X 10.7 or later, open LaunchPad. Click Utilities, then Console in the page that opens.

Step 1

Select "system.log" from the file list. Enter "BOOT_TIME" (without the quotes) in the search box. Note the times of the log messages referring to boot times. Now clear the search box and scroll back in the log to the last boot time when you had the problem. Post the messages logged during the time something abnormal was happening. That time might be before or after the boot.

For example, if the problem is a slow startup taking three minutes, post the messages timestamped within three minutes after the boot time, not before. If the problem is a system crash or freeze, post the messages from before the boot time, when the system was about to crash or freeze. In either case, please include the BOOT_TIME message at the beginning or the end of the log extract.

Post the log text, please, not a screenshot. If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message.

If the log doesn't go back far enough in time, scroll down in the Console file list to /private/var/log/system.log.0.bz2. Search that archived log, and if necessary the older ones below it, for the same information.

Important: Some private information, such as your name, may appear in the log. Edit it out by search-and-replace in a text editor before posting.

Step 2

Do the same with kernel.log.

Step 3

Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the most recent one, if any. 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.) Pleasedon’t post shutdownStall or hang logs — they're very long and not helpful.

Reply

Answer 2

kevofoz Author

Level 1

8 points

May 11, 2012 6:54 AM in response to Linc Davis

Hi Linc,

Thanks for responding to my post. FYI Safari updated to v5.7.1, exactly the same problem occured this evening.

Extracts you have requested from the logs for the MBP is set out below.

Extract from system.log

May 11 21:42:38 ****-macbook-pro Safari[1478]: Performance: Please update this scripting addition to supply a value for ThreadSafe for each event handler: "/Library/ScriptingAdditions/SIMBL.osax"

May 11 21:42:39 ****-macbook-pro com.apple.launchd[1] (com.synium.cleanappdaemon[1486]): posix_spawn("/Library/Application Support/CleanApp/CleanApp Daemon.app/Contents/MacOS/CleanApp Daemon", ...): No such file or directory

May 11 21:42:39 ****-macbook-pro com.apple.launchd[1] (com.synium.cleanappdaemon[1486]): Exited with exit code: 1

May 11 21:42:39 ****-macbook-pro com.apple.launchd[1] (com.synium.cleanappdaemon): Throttling respawn: Will start in 10 seconds

May 11 21:42:40 ****-macbook-pro sandboxd[1488]: cvmsComp_i386(1487) deny mach-lookup com.intego.mig_hook

May 11 21:42:45 ****-macbook-pro Safari[1478]: MDS Error: unable to create user DBs in /var/folders/OC/OCSndytXGQCI8MvWul3HRE+++TI/-Caches-//mds

May 11 21:42:47: --- last message repeated 5 times ---

May 11 21:42:47 ****-macbook-pro /System/Library/Frameworks/PubSub.framework/Versions/A/Resources/PubSubAgent.ap p/Contents/MacOS/PubSubAgent[1491]: MDS Error: unable to create user DBs in /var/folders/OC/OCSndytXGQCI8MvWul3HRE+++TI/-Caches-//mds****

May 11 21:42:48: --- last message repeated 8 times ---

May 11 21:42:48 ****-macbook-pro Safari[1478]: InjectEventHandler

May 11 21:42:49 ****-macbook-pro Safari[1478]: Safari Cookies loaded from: /Library/Application Support/SIMBL/Plugins/Safari Cookies.bundle

May 11 21:43:05 ****-macbook-pro WebProcess[1480]: INSERT-HANG-DETECTED: Tx time:4.436137, # of Inserts: 3, # of bytes written: 111793, Did shrink: NO

May 11 21:43:13 ****-macbook-pro WebProcess[1480]: INSERT-HANG-DETECTED: Tx time:7.939700, # of Inserts: 3, # of bytes written: 101036, Did shrink: NO

May 11 22:09:02 localhost fseventsd[33]: event logs in /.fseventsd out of sync with volume. destroying old logs. (17775 22 17851)

May 11 22:09:03 localhost fseventsd[33]: log dir: /.fseventsd getting new uuid:

May 11 22:09:04 localhost bootlog[41]: BOOT_TIME: 1336738120 0

May 11 22:09:04 localhost DirectoryService[38]: Improper shutdown detected

Extract from kernel.log

May 11 21:37:55 ****-macbook-pro kernel[0]: ::dequeueData: - Interrupted!

May 11 21:37:55 ****-macbook-pro kernel[0]: ::dataReadComplete: Read complete io error.

May 11 21:38:13 ****-macbook-pro kernel[0]: ::acquirePort: - Start read.!

May 11 22:09:02 localhost kernel[0]: npvhash=4095

May 11 22:09:02 localhost kernel[0]: PAE enabled

May 11 22:09:02 localhost kernel[0]: 64 bit mode enabled

May 11 22:09:02 localhost kernel[0]: Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386

May 11 22:09:02 localhost kernel[0]: vm_page_bootstrap: 949518 free pages and 25330 wired pages

May 11 22:09:02 localhost kernel[0]: standard timeslicing quantum is 10000 us

May 11 22:09:02 localhost kernel[0]: mig_table_max_displ = 73

May 11 22:09:02 localhost kernel[0]: AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled

May 11 22:09:02 localhost kernel[0]: calling mpo_policy_init for TMSafetyNet

May 11 22:09:02 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)

May 11 22:09:02 localhost kernel[0]: calling mpo_policy_init for Quarantine

May 11 22:09:02 localhost kernel[0]: Security policy loaded: Quarantine policy (Quarantine)

May 11 22:09:02 localhost kernel[0]: calling mpo_policy_init for Sandbox

May 11 22:09:02 localhost kernel[0]: Security policy loaded: Seatbelt sandbox policy (Sandbox)

May 11 22:09:02 localhost kernel[0]: MAC Framework successfully initialized

May 11 22:09:02 localhost kernel[0]: using 16384 buffer headers and

4096 cluster IO buffer headers

May 11 22:09:02 localhost kernel[0]: IOAPIC: Version 0x11 Vectors 64:87

May 11 22:09:02 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)

May 11 22:09:02 localhost kernel[0]: PFM64 0xf10000000, 0xf0000000

May 11 22:09:02 localhost kernel[0]: [ PCI configuration begin ]

May 11 22:09:02 localhost kernel[0]: console relocated to 0xf10010000

May 11 22:09:02 localhost kernel[0]: PCI configuration changed (bridge=2 device=1 cardbus=0)

May 11 22:09:02 localhost kernel[0]: [ PCI configuration end, bridges 5 devices 18 ]

May 11 22:09:02 localhost kernel[0]: AppleIntelCPUPowerManagement: (built 16:44:45 Jun 7 2011) initialization complete

May 11 22:09:02 localhost kernel[0]: mbinit: done (64 MB memory set for mbuf pool)

May 11 22:09:02 localhost kernel[0]: USBF: 0.345 AppleUSBOHCI[0x8455800]::InitializeOperationalRegisters Non-NULL hcDoneHead: 0xadb58480

May 11 22:09:02 localhost kernel[0]: rooting via boot-uuid from /chosen:

Most recent crash log

Crashed Thread: 2

Thread 2 Crashed:

Thread 2 crashed with X86 Thread State (64-bit):

0x7fff82659000 - 0x7fff82664fff com.apple.CrashReporterSupport 10.6.7 (258) /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/Cra shReporterSupport

Look forward to hearing from you. Thanks again for your assistance.

Reply

Answer 3

Linc Davis

Level 10

209,547 points

May 11, 2012 9:22 AM in response to kevofoz

The kernel log extract is post-boot, not pre-boot, and the crash log extract is useless because it's incomplete, but from the information provided, I suggest you uninstall SIMBL as follows.

Select Go ▹ Go to Folder… from the Finder menu bar, then enter the following text in the box that opens:

/Library

A folder will open. From that folder, delete the items listed below (some may be absent.) You may be prompted for your administrator login password.

Application Support/SIMBL

InputManagers/SIMBL.bundle

LaunchAgents/net.culater.SIMBL.Agent.plist

ScriptingAdditions/SIMBL.osax

Log out and log back in.

Make sure you never reinstall SIMBL. It’s likely to come bundled with another third-party system modfication that depends on it. If you want trouble-free computing, avoid software that makes miraculous changes to other software, especially built-in applications. The only real exception to that rule is Safari extensions, which are mostly safe, and are easy to get rid of when they don’t work. SIMBL and its dependents are not Safari extensions.

Reply

Answer 4

kevofoz Author

Level 1

8 points

May 12, 2012 11:05 PM in response to Linc Davis

Hi Linc,

Uninstalled the SIMBL items as you suggested.

I'm pleased to say that Safari has been stable all day.

Thankyou so much for your help with this.

Cheers

Reply