Q: Safari 8 on Yosemite spawns process causing a CPU load spike
My Safari 8 running on MacBook Pro (Late 2013)/Yosemite was hijacked by Open-Search.com after updating OS to Yosemite 10.10. The affect seems two fold, my home page was hijacked by Open-Search/MacKeeper and the CPU started to load spikes at regular intervals. After a lot of digging I've removed the resources for Open-Search/MacKeeper ending the hijack. However distnoted, SubPubAgent and nsurlstoraged are showing up in the Activity Monitor and dumping the following log entry in the Message log file
11/3/14 12:58:35.657 PM nsurlstoraged[233]: DiskCookieStorage changing policy from 2 to 0, cookie file: ///Users/<username>/Library/Cookies/Cookies.binarycookies
11/3/14 12:58:35.658 PM nsurlstoraged[233]: DiskCookieStorage changing policy from 0 to 2, cookie file: ///Users/<username>/Library/Cookies/Cookies.binarycookies
This entry repeats about 4000 times spiking the CPU over 300% and actuating the fan, making Safari dangerous to run. Once I quit out of Safari, the process ends and everything runs as expected. Here is the whole Safari launch process.
11/3/14 3:28:46.598 PM nsurlstoraged[232]: DiskCookieStorage changing policy from 0 to 2, cookie file: file:///Users/username/Library/Cookies/Cookies.binarycookies
11/3/14 3:28:46.613 PM storeaccountd[285]: AccountServiceDelegate: Accepting new connection <NSXPCConnection: 0x7fb9bd818dd0> connection from pid 538 with interface <AccountServiceInterface: 0x7fb9bd81fbe0> (PID 538)
11/3/14 3:28:46.728 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
11/3/14 3:28:46.765 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
11/3/14 3:28:46.927 PM locationd[55]: Couldn't find a requirement string for masquerading client /System/Library/PrivateFrameworks/Parsec.framework
11/3/14 3:28:46.928 PM locationd[55]: could not get apple languages array, assuming english
11/3/14 3:28:46.930 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
11/3/14 3:21:19.295 PM com.apple.xpc.launchd[1]: (com.apple.PubSub.Agent[503]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.pubsub.ipc
11/3/14 3:21:19.295 PM com.apple.xpc.launchd[1]: (com.apple.PubSub.Agent[503]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.pubsub.notification
11/3/14 3:21:56.010 PM CoreServicesUIAgent[240]: unexpected message <OS_xpc_error: <error: 0x7fff7bd13c60> { count = 1, contents = "XPCErrorDescription" => <string: 0x7fff7bd13f70> { length = 18, contents = "Connection invalid" }}>
11/3/14 3:22:29.019 PM nsurlstoraged[232]: DiskCookieStorage changing policy from 0 to 2, cookie file: file:///Users/username/Library/Cookies/Cookies.binarycookies
11/3/14 3:22:29.020 PM nsurlstoraged[232]: DiskCookieStorage changing policy from 2 to 0, cookie file: file:///Users/username/Library/Cookies/Cookies.binarycookies
I've tried a couple things including adding the log file do_dnserver_log with `touch /var/log/do_dnserver_log`. This minimized the problem, but didn't solve it. The CPU load is still intermittently spiking and the system.log filing with DiskCookieStorage entries. Any help is appreciated since I use Safari for development work.
Regards
Ron
MacBook Pro, OS X Yosemite (10.10)
Posted on Nov 3, 2014 1:37 PM
Hi Linc,
I had and used your post earlier to help remove the VSearch files and resources. The CPU was still spiking after the fact. I was able to get it figured out though with the help of another guy over at StackExchange - Ask Different. Here are the additional steps required to get my situation corrected:
Step 1: sudo rm -f ~/Library/Cookies/Cookies.binarycookies
enter password
Step 2: Select Clear History and Website Data from Safari menu; click Clear History button in dialog box. This resets Safari
Step 3: Then force quit Safari from the context menu by clicking Cnt + icon in the dock.
Step 4: Finally, fully power down (Shut Down not Restart) the machine and then restart.
These steps in addition to your steps above finally fixed the problem, at least for my setup. Thanks for the feedback and your original post.
Ron
Posted on Nov 3, 2014 5:25 PM