PDA

View Full Version : Mdworker (Launchd) using CPU 100%




srinivasnarne
Sep 20, 2012, 09:20 AM
I'm using 10.8.2. I've observed today in the activity monitor that "mdworker" is using 100% of my CPU. When I click the 'inspect' button it showed "launchd" as the parent process for "mdworker". My CPU temperature is in between 70 to 80 celcius. This is going on from the last 3-4 hours. My harddisk has almost 75% free space of the total space(500GB). The spotlight search icon in the menu bar is blank(No dot in it) i.e., spotlight is not indexing. Why is this happening even though when spotlight is not indexing?

I've not connected or mounted any external drives. I've installed skydrive app a few days ago. I've updated to 10.8.2 last night. And I've also installed the Macbook pro 2012 firmware update released last night for non retina mid 2012 models.



Weaselboy
Sep 20, 2012, 09:40 AM
Enter the command below in Terminal and that will reindex Spotlight. You will be prompted for your password.

sudo mdutil -E /

jonathan.muth
Sep 20, 2012, 09:56 AM
I have got the same problem here. Mdworker and Mds take up between 40% and 60% of my CPU resources. Excluding all drives from Spotlight does not make a difference. Neither does reindexing.

According to some other threads it has some thing to do with:

mdworker[299]: Unable to talk to lsboxd

sandboxd[296] ([299]): mdworker(299) deny mach-lookup com.apple.ls.boxd


kernel[0]: Sandbox: sandboxd(314) deny mach-lookup com.apple.coresymbolicationd


Lets hope somebody finds a fix.

50548
Sep 21, 2012, 11:06 AM
I have got the same problem here. Mdworker and Mds take up between 40% and 60% of my CPU resources. Excluding all drives from Spotlight does not make a difference. Neither does reindexing.

According to some other threads it has some thing to do with:







Lets hope somebody finds a fix.

Facing similar problems here, and also wake-from-sleep issues that had not happened under 10.8.1. Does anyone know where to find the ls file mentioned above?

50548
Sep 21, 2012, 11:18 AM
Facing similar problems here, and also wake-from-sleep issues that had not happened under 10.8.1. Does anyone know where to find the ls file mentioned above?

Guys, I may (just may) have found the culprit: I looked for the aforementioned files and found them under Computer>Library (NOT YOUR USER LIBRARY)>Caches.

In there, there was a folder called "coresymbolicationd" with a red "no entry" sign on it (due perhaps to a permissions issue or a deprecated file) - I deleted all of them.

Console still shows messages like the above, so I will try to restart/sleep and see if the problem continues.

50548
Sep 21, 2012, 01:21 PM
Mods, can you move this thread to the ML section? This is not just about MBP.

Mod Note: Thread moved. But please report the thread and ask for it to be moved rather than requesting moderation in the thread.

gwang73
Sep 21, 2012, 08:42 PM
Guys, I may (just may) have found the culprit: I looked for the aforementioned files and found them under Computer>Library (NOT YOUR USER LIBRARY)>Caches.

In there, there was a folder called "coresymbolicationd" with a red "no entry" sign on it (due perhaps to a permissions issue or a deprecated file) - I deleted all of them.

Console still shows messages like the above, so I will try to restart/sleep and see if the problem continues.

I'm not sure if this was the culprit, but I've managed to fix my system. I removed the /Library/Caches/com.apple.coresymbolicationd folder. You'll need to CMD-I and add permissions for admin or your username before deleting.

I didn't have enough patience to see if it fixed it or not, but I re-installed ML by rebooting into recovery mode, CMD-R, and re-installed ML. I no longer get any mdworker errors in system logs. After re-install, the com.apple.coresymbolicationd folder is no longer there.

Hope this helps.

PossumBoy
Nov 9, 2013, 11:19 PM
I had the same issues as what you had mentioned until I stumbled onto this thread : http://forums.macrumors.com/showthread.php?p=18341143

Problems with spotlight constantly indexing after moving over to mavericks seem to have fixed now.