Skip navigation

Google Chrome causing system to freeze

240 Views 0 Replies Latest reply: Feb 5, 2013 5:01 AM by plogue1987 RSS
plogue1987 Calculating status...
Currently Being Moderated
Feb 5, 2013 5:01 AM

Google Chrome has been sporadically causing my system to freeze. It may work fine for a few days, or for less than twenty-four hours. Without warning, the browser will suddenly begin reading and waiting on its cache, and become unresponsive. When I try to force quit the application, the system locks up and Finder will freeze but imputs are still responsive, causing me to have to do a hard reboot. Once rebooted, Spotlight re-indexes my hard drive [which I believe is a separate issue (mdworker unable to talk to lsboxd)]. This only occurs with Google Chrome and is not replicable with other browsers or applications.


I have cleared all caches and reset my PRAM and SMC controller, but the issue persists. Any thoughts?


System info:

Early 2008 Macbook Pro (4,1)

OS 10.8.2

Chrome Version: 24.0.1312.57

Extensions: Disconnect 4.2.0, DoNotTrackMe, Ghostery 4.1.0, Reddit Enhancement Suite 4.1.5


Console log up until forced reboot:

2/5/13 12:40:06.603 PM mdworker[5062]: Unable to talk to lsboxd

2/5/13 12:40:07.000 PM kernel[0]: Sandbox: sandboxd(5063) deny mach-lookup

2/5/13 12:40:07.457 PM sandboxd[5063]: ([5062]) mdworker(5062) deny mach-lookup

2/5/13 12:42:08.365 PM mdworker[5066]: Unable to talk to lsboxd

2/5/13 12:42:08.629 PM sandboxd[5067]: ([5066]) mdworker(5066) deny mach-lookup

2/5/13 12:42:08.000 PM kernel[0]: Sandbox: sandboxd(5067) deny mach-lookup

2/5/13 12:45:27.000 PM kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=5071[GoogleSoftwareUp] clearing CS_VALID

2/5/13 12:46:10.892 PM mdworker[5074]: Unable to talk to lsboxd

2/5/13 12:46:11.000 PM kernel[0]: Sandbox: sandboxd(5075) deny mach-lookup

2/5/13 12:46:11.634 PM sandboxd[5075]: ([5074]) mdworker(5074) deny mach-lookup

2/5/13 12:46:48.837 PM WindowServer[101]: Created shield window 0x685 for display 0x042720c0

2/5/13 12:46:48.837 PM WindowServer[101]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x0(0)

2/5/13 12:46:48.849 PM WindowServer[101]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x0(0)

2/5/13 12:47:41.744 PM WindowServer[101]: handle_will_sleep_auth_and_shield_windows: no lock state data

2/5/13 12:50:41.653 PM mdworker[5094]: Unable to talk to lsboxd

2/5/13 12:50:42.000 PM kernel[0]: Sandbox: sandboxd(5095) deny mach-lookup

2/5/13 12:50:42.217 PM sandboxd[5095]: ([5094]) mdworker(5094) deny mach-lookup

2/5/13 12:51:51.000 PM kernel[0]: nspace-handler-set-snapshot-time: 1360065113

2/5/13 1:00:54.000 PM bootlog[0]: BOOT_TIME 1360065654 0

MacBook Pro, OS X Mountain Lion (10.8.2), Early 2008 MBP (4,1)


More Like This

  • Retrieving data ...

Bookmarked By (0)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.