-
All replies
-
Helpful answers
-
Feb 4, 2015 4:53 PM in response to tchekaldby Linc Davis,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.
☞ Open LaunchPad and start typing the name.
The title of the Console window should be All Messages. If it isn't, select
SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar at the top of the screen.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter "mccon" (without the quotes.)
You may now see some lines in the log referring to "MCContactsManager". Select the last few such lines, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
☞ You should post no more than 5 lines.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
☞ Some private information, such as your name, may appear in the log. Anonymize before posting.
-
Feb 5, 2015 1:07 AM in response to Linc Davisby tchekald,Hello,
Unfortunately nothing comes up when I search for “mccon” - there was nothing to select.
By the way, the parent process for recentsd and Calncseervice is indicated as “launchd (1)”.
Shall I try to get additional info for you?
Thank you,
Dmitri
-
Feb 5, 2015 10:15 AM in response to tchekaldby Linc Davis,When you have the problem, note the exact time: hour, minute, second.
These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
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.
☞ Open LaunchPad and start typing the name.
The title of the Console window should be All Messages. If it isn't, select
SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar at the top of the screen.
Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.
Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.
Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
Some private information, such as your name, may appear in the log. Anonymize before posting.
-
Feb 6, 2015 11:51 AM in response to Linc Davisby tchekald,Hello,
Please find below Console messages as requested.
You wil notice that first message is when process CalNCService was caught burning CPU.
There is another one at 01:39:21 process recentsd[341] thread 4786 caught burning CPU! It used more than 50% CPU (Actual recent usage: 76%) over 180 seconds. thread lifetime cpu usage 90.032142 seconds, (89.079034 user, 0.953108 system) ledger info: balance: 90001225538 credit: 90001225538 debit: 0 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 117044255650
When I start Mac CalNCservice appears first, which is followed by process recentsd if I open Mail…
Thank you!
D
07/02/15 01:36:01,000 kernel[0]: process CalNCService[227] thread 2191 caught burning CPU! It used more than 50% CPU (Actual recent usage: 85%) over 180 seconds. thread lifetime cpu usage 90.011023 seconds, (89.257281 user, 0.753742 system) ledger info: balance: 90002359557 credit: 90002359557 debit: 0 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 105773339065
07/02/15 01:36:02,170 com.apple.xpc.launchd[1]: (com.apple.ReportCrash[317]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash
07/02/15 01:36:02,171 ReportCrash[317]: Invoking spindump for pid=227 thread=2191 percent_cpu=85 duration=106 because of excessive cpu utilization
07/02/15 01:36:04,792 spindump[318]: Saved cpu_resource.diag report for CalNCService version 1.0 (316) to /Library/Logs/DiagnosticReports/CalNCService_2015-02-07-013604_Dmitri-Computer. cpu_resource.diag
07/02/15 01:36:20,439 WDMemeod[39]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.2 instead of 10.10.2. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
Call location:
07/02/15 01:36:20,592 WDMemeod[39]: 0 CarbonCore 0x927df7c7 ___Gestalt_SystemVersion_block_invoke + 135
07/02/15 01:36:20,593 WDMemeod[39]: 1 libdispatch.dylib 0x921c2130 dispatchclient_callout + 50
07/02/15 01:36:20,593 WDMemeod[39]: 2 libdispatch.dylib 0x921c20b5 dispatch_once_f + 251
07/02/15 01:36:20,593 WDMemeod[39]: 3 libdispatch.dylib 0x921c30d8 dispatch_once + 31
07/02/15 01:36:20,593 WDMemeod[39]: 4 CarbonCore 0x92771e88 GestaltSystemVersion + 1050
07/02/15 01:36:20,594 WDMemeod[39]: 5 CarbonCore 0x92771a39 Gestalt + 150
07/02/15 01:36:20,594 WDMemeod[39]: 6 WDMemeod 0x00051439 WDMemeod + 328761
07/02/15 01:36:20,000 kernel[0]: fsevents: watcher WDMemeod (pid: 39) - Using /dev/fsevents directly is unsupported. Migrate to FSEventsFramework
07/02/15 01:36:23,666 mdworker[294]: code validation failed in the process of getting signing information: Error Domain=NSOSStatusErrorDomain Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"
07/02/15 01:36:43,723 SystemUIServer[196]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
07/02/15 01:36:43,744 mdworker[297]: code validation failed in the process of getting signing information: Error Domain=NSOSStatusErrorDomain Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"
07/02/15 01:36:59,354 mdworker[329]: code validation failed in the process of getting signing information: Error Domain=NSOSStatusErrorDomain Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"
07/02/15 01:37:19,816 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
07/02/15 01:37:23,678 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
07/02/15 01:37:23,726 Mail[336]: No worthy mechs found
07/02/15 01:37:23,726 Mail[336]: No worthy mechs found
07/02/15 01:37:23,720 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
07/02/15 01:37:25,419 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
07/02/15 01:37:25,478 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
07/02/15 01:37:26,229 Mail[336]: No worthy mechs found
07/02/15 01:37:26,230 Mail[336]: No worthy mechs found
07/02/15 01:37:28,159 Mail[336]: No worthy mechs found
07/02/15 01:37:28,160 Mail[336]: No worthy mechs found
07/02/15 01:37:29,090 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
07/02/15 01:37:29,968 Mail[336]: No worthy mechs found
07/02/15 01:37:29,969 Mail[336]: No worthy mechs found
07/02/15 01:37:55,657 mds[32]: (Volume.Normal:2464) volume:0x7fe051186e00 ********** Bootstrapped Creating a default store:0 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/firmwaresyncd.VvsbIn
07/02/15 01:39:21,000 kernel[0]: process recentsd[341] thread 4786 caught burning CPU! It used more than 50% CPU (Actual recent usage: 76%) over 180 seconds. thread lifetime cpu usage 90.032142 seconds, (89.079034 user, 0.953108 system) ledger info: balance: 90001225538 credit: 90001225538 debit: 0 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 117044255650
07/02/15 01:39:21,623 com.apple.xpc.launchd[1]: (com.apple.ReportCrash[363]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash
07/02/15 01:39:21,624 ReportCrash[363]: Invoking spindump for pid=341 thread=4786 percent_cpu=76 duration=119 because of excessive cpu utilization
07/02/15 01:39:31,209 spindump[318]: Saved cpu_resource.diag report for recentsd version ??? (???) to /Library/Logs/DiagnosticReports/recentsd_2015-02-07-013931_Dmitri-Computer.cpu_ resource.diag
07/02/15 01:39:41,182 com.apple.SecurityServer[55]: Killing auth hosts
07/02/15 01:39:41,182 com.apple.SecurityServer[55]: Session 100011 destroyed
-
Feb 8, 2015 12:56 PM in response to tchekaldby Linc Davis,Back up all data before proceeding.
Triple-click anywhere in the line below on this page to select it:
~/Library/Containers/com.apple.CalendarAgent.CalNCService
Right-click or control-click the line and select
Services ▹ Reveal in Finder (or just Reveal)
from the contextual menu.* A folder should open with an item selected. Move the selected item to the Trash.
Repeat with this item:
~/Library/Containers/com.apple.corerecents.recentsd
Log out or restart the computer and test.
*If you don't see the contextual menu item, copy the selected text to the Clipboard by pressing the key combination command-C. In the Finder, select
Go ▹ Go to Folder...
from the menu bar and paste into the box that opens by pressing command-V. You won't see what you pasted because a line break is included. Press return.
-
Feb 17, 2015 5:45 AM in response to Linc Davisby Petr Sponer,Hi Everybody,
I am experiencing very similar problem on my MacBook. OS X 10.10.2, MacBook Pro (Retina, 13-inch, Mid 2014).
In my case there are usually 3 highly CPU consuming processes - CalNCService, usernoted, recentsd. I have to always kill the processes and then I have a chance to live on battery for 1-2 hours. But before that problem occured it was twice the time. The processes always re-emerge after wake Mac from sleep.
Your hint unfortunately doesn`t seem working for me. Any other idea? Thanks.
-
Apr 21, 2015 2:21 AM in response to Petr Sponerby mija15,Hey there,
Have you found a way to resolve your problem? I'm having the exact same thing happen with the same processes and haven't been able to sort it out
-
Jun 18, 2015 4:14 PM in response to Petr Sponerby winstonwolfau,Peter I've got the same issue.
I've got a 2012 rmbp 13, 8GB and 512 disk running Yosemite.
I just end up force quitting these processes several times and then the CPU goes down. I find it frustrating that I have to do this everytime i wake the laptop from sleep else my battery s gone.
Very disappointed, I think I will try a re-install of OSX if I can't get this fixed on the weekend.
-
Jul 22, 2015 6:02 PM in response to tchekaldby Da G33k,I recently resolved this issue on my mom's iMac and MacBook Air. The problem wasn't with Mac Mail though, but was with some online IMAP settings.
My mom has multiple email accounts on her Mac Mail, including some Gmail accounts and one Google Apps account. After manually disabling each account under Mail - Preferences - Accounts, she was able to determine that the cause of recentsd and CalNCService using so much CPU and memory was coming from her Google Apps account. After going to Settings - Forwarding and POP/IMAP and comparing her settings with another Google Apps account that wasn't having any problems, I noticed that Auto-Expunge was turned off. After I turned Auto-Expunge on, the problem went away after re-enabling her email account in Preferences - Accounts.
Although this was a Google Apps email account, it would probably apply to any Gmail account as well.
Hopefully this helps some of you.
-
Sep 4, 2015 1:20 AM in response to tchekaldby Jonahmc,I also had this issue. I was able to resolve it by disabling notifications (System Preferences > Notifications) in various apps for which I do not require the notifications. I would not have hesitated, however, to disable notifications for all apps if it were necessary in my quest to reclaim the CPU.
I'm glad to have it back. Best of luck to y'all.
-
Nov 20, 2015 2:27 PM in response to tchekaldby lulhannes,Having same issues with these processes. The following worked for me (iMac - Yosemite)
- disable all e-mail accounts (Gmail)
- enable them one-by-one and keep an eye on CPU and Mem usage
- after enabling certain account, CPU and Mem usage increased steeply; when disabling account CPU and Mem. back to normal
- as it appeared the issues hinged on this single e-mail account, more specific the calendar being synchronized
- disabled calendar from synchronizing; issue resolved
Next is finding root cause of calendar issues, but disabling it made that I can use my Imac normally again!
