Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Atsserver and mdworker

Ive had 5 clean installs so far. (whew) However on my c2d 17" mbpro atsserver and mdworker have now been running at ~20-40% cpu for 5 hours. Ive killed them etc etc. I know its usually a font cache problem, But Ive yet to find any font caches in the normal areas. Anyone else having this problem?? Thanks

Codeslave

17" c2d mbp, Mac OS X (10.5)

Posted on Oct 26, 2007 6:58 PM

Reply
24 replies

Oct 27, 2007 7:13 AM in response to Codeslave

I think I got it. I wasn't using my admin account, even though my personal account has admin privileges. So I logged into the admin account, and while Spotlight was indexing, mdworker wasn't showing up in the Activity Monitor, and CPU resources were fine. Indexing was done after about an hour and a half, then I logged back into my personal account, and everything seems back to normal.

Oct 30, 2007 3:31 AM in response to Codeslave

My MBP (Early 2006) is having a fit with ATSServer - it consumes up to 99% of my processor at times. It can't be Spotlight indexing, unless it takes Spotlight 3 1/2 days to index. Everything is so s-l-o-w with ATSServer consuming so much precious processor time.

There must be a solution... can anyone offer any suggestions or solutions?

Oct 31, 2007 1:17 AM in response to cbd2

cbd2 wrote:
I just got smart and checked Software Update and there is are two updates - "Login & Keychain Update" and "Remote Desktop Client" - one of which seems to solve the problem. There is one other update as well, "Backup", but I suspect "Login & Keychain Update" to be the problem solver.


Reply to myself yet again...

No, those updates didn't really 'fix' the problem at all... just delays it somewhat. Having three apps open and doing nothing the processors were again maxing out at 100% usage each. Just now I'm at 100% and 16% and it's Atsserver and mdworker that are hogging the load. Anyone else find a solution yet?

Nov 2, 2007 5:55 AM in response to whuggy

Ah! Therein may lie my problem (!?). On one folder, on one external drive, I have a folder of over 2,000 pdf files which range in page count from as little as 200 to as many as 1,400 pages. I'll try including the 2 250Gb Firewire drives (which I've made 'Private') and only 'privatizing' that one folder. If all indexes over the weekend - fine. If not, it's back to square one.

Nov 9, 2007 9:20 PM in response to cbd2

Switch what you don't want indexed to private, let it do what it needs to index the rest.

You can alleviate the CPU hogging to a degree by reniceing the process.

renice -n 19 -p pid ofmdworker
renice -n 19 -p pid ofATSServer

Seems like a resource hog to me, but I don't remember if it was any worse with Tiger.

Atsserver and mdworker

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.