|
Replies
:
19
-
Pages
:
2
[
1
2
|
Next
]
-
Last Post
:
Apr 28, 2009 2:02 PM
by: RichardLloyd
|
|
|
Posts:
4
From:
SF Bay Area
Registered:
Oct 7, 2008
|
|
|
|
ATSServer CPU @ 200% LOCKS-UP Mac Pro dual quad-core desktop
Posted:
Oct 7, 2008 5:44 AM
|
|
|
My dual quad core running Mac OS X 10.5.5 locks-up frequently at boot.
Required hard (destructive) reboot, until I figured out workaround
described below. Apple really needs to fix this as a high priority.
Symptom: Desktop freezes and the system becomes unusable.
Usually occurs when booting the system, but can happen
at other times spontaneously.
When it occurs during boot (after desktop first appears, usually
as task bar is starting to populate), the wedging is so bad that
applications are effectively 'suspended' mid-launch.
Icons and menu and mouse buttons and keyboard completely unresponsive.
Usually just a spinning beach ball that tracks with the mouse is present.
Attempts to resolve (both failed):
1. Did a fresh install of Mac OS X (with data transfer) and upgraded,
which brought system to 10.5.5. (Problem appeared immediately
on fresh installed system).
2. Totally re-indexed Spotlight and de-selected option to not index
PDF documents.
Workaround:
1. Enable 'ssh' logins and root user.
2. Login via 'ssh' from remote system, while Mac Pro desktop frozen.
3. Become super user in 'ssh' session.
4. Find ATSServer with 'ps -ef' or 'top' command.
5. Terminate ATSServer with 'kill -9'
6. Desktop on Mac Pro immediately unwedges and applications
that hung during start-up finish launching.
/var/log/system.log (many messages like this):
System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Support/ATSServer241: FOExceptionMainHandler caught a fatal exception at 0x96028036
Safari151: GCGetStrikeMetrics failed: error 5.
Plea from customer:
Apple: PLEASE post an update to fix this very soon.
If anyone has clear instructions on what I can do to fix properly until
Apple comes up with a real fix, for example, caches to clear,
how to identify a faulty file, or quarantine a faulty faunt,
or any other diagnostics, please feel free to reply.
My machine was already in the shop for five weeks recently for repair,
and I can't afford down time, because I'm mid-project right now,
and it will be a HUGE setback to have to bring my machine into the
shop again for another 'n' days.
Mac Pro (8-core, 3.0 GHz)
Mac OS X (10.5.5)
|
|
Posts:
4,704
From:
SF Bay Area
Registered:
May 3, 2004
|
|
|
|
Re: ATSServer CPU @ 200% LOCKS-UP Mac Pro dual quad-core desktop
Posted:
Oct 7, 2008 6:03 AM
in response to: agent_of_fortune
|
|
|
"ATSServr is a system daemon which provides font management and processing." (from the manual page.)
I'd take a look at what fonts are installed.
MacBook 2.0GhzCore2Duo, 2Gig, 160G HD, PowerBook G4 1.5Ghz 15"
Mac OS X (10.5.4)
Logic Studio 8, Focusrite Saffire
|
|
Posts:
4
From:
SF Bay Area
Registered:
Oct 7, 2008
|
|
|
|
Re: ATSServer CPU @ 200% LOCKS-UP Mac Pro dual quad-core desktop
Posted:
Oct 7, 2008 10:13 AM
in response to: tele_player
|
|
|
Too many fonts installed to have a clue without
some sort of trace of debugging output of ATSServer to figure out what it's
barfing on.
Mac Pro (8-core, 3.0 GHz)
Mac OS X (10.5.5)
|
|
Posts:
14,976
From:
Sweet Home, Chicago
Registered:
Jan 11, 2001
|
|
|
|
Re: ATSServer CPU @ 200% LOCKS-UP Mac Pro dual quad-core desktop
Posted:
Oct 7, 2008 10:19 AM
in response to: agent_of_fortune
|
|
|
I suggest you ditch all your fonts, and use a dedicated font manager such as Suitcase or Linotype Font Explorer, activating only those fonts you need at any given time so the ATS server doesn't have to work so hard.
Try also ditching the ATS cache by running this Terminal command atsutil databases -remove
iMac 2.66Ghz, 2.4Ghz MacBook Pro, iPhone 3G
Mac OS X (10.5.4)
|
|
Posts:
9
Registered:
Nov 8, 2006
|
|
|
|
Re: ATSServer CPU @ 200% LOCKS-UP Mac Pro dual quad-core desktop
Posted:
Oct 9, 2008 6:52 AM
in response to: agent_of_fortune
|
|
|
I can confirm the same problem. On my system it has nothing to do with fonts. It seems that QuickLook is the culprit as the error is reproducible when I click on a particular folder and I get errors like this in system log:
09.10.08 15:47:26 quicklookd227 QL ERROR 'Creating thumbnail' timed out for '<QLThumbnailRequest /Users/...>'
Manually killing the ATSServer and leaving the folder seems to be the only solution otherwise a hard reboot is required. This is a major problem.
MacBook
Mac OS X (10.5.5)
|
|
Posts:
4
From:
SF Bay Area
Registered:
Oct 7, 2008
|
|
|
|
Re: ATSServer CPU @ 200% LOCKS-UP Mac Pro dual quad-core desktop
Posted:
Oct 16, 2008 3:37 AM
in response to: Charlie_X
|
|
|
I am questioning whether or not it has anything to do with fonts as well. I spent $100 and bought "Suitcase Fusion", and I'm configuring my system with that. We'll see. Having spotlight re-index and
exclude PDF's and fonts doesn't fix it.
Everytime I reboot now I have the problem, and for some reason killing ATSServer a couple of times from an ssh login stops it. I'm still trying to figure out what the **** is going on.
I don't see any quicklookd error messages in /var/log/system.log, However, grepping for Quick shows me that quicklook is one of the processes monitoring ATSserver, and like the others, logs a message that ATSServer died when I terminate it.
I hope this is addressed in the next update, and that the update is forthcoming.
Mac Pro (8-core, 3.0 GHz)
Mac OS X (10.5.5)
|
|
Posts:
3
From:
Brooklyn
Registered:
Oct 18, 2008
|
|
|
|
Re: ATSServer CPU @ 200% LOCKS-UP Mac Pro dual quad-core desktop
Posted:
Oct 18, 2008 10:13 AM
in response to: agent_of_fortune
|
|
|
I'm also seeing this problem on my MacBook with 10.5.5. After killing ATSServer via ssh, I looked in the Console, and found these console messages which occurred when the GUI locked up:
10/18/08 12:44:03 PM com.apple.ATSServer2554 Notice ATSServer(2554,0xa076afa0) malloc: *** error for object 0x83ac00: incorrect checksum for freed object - object was probably modified after being freed.
10/18/08 12:44:03 PM com.apple.ATSServer2554 Notice *** set a breakpoint in malloc_error_break to debug
The problem seems to happen whenever I mount a certain remote shared volume (AppleShare) from my old desktop computer (G4 Dual 450 running 10.4.11). I guess it could be that ATSServer is choking when trying to generate QuickLook previews for some document on the shared volume...
MacBook
Mac OS X (10.5.5)
|
|
Posts:
3
From:
Brooklyn
Registered:
Oct 18, 2008
|
|
|
|
Re: ATSServer CPU @ 200% LOCKS-UP Mac Pro dual quad-core desktop
Posted:
Oct 18, 2008 10:28 AM
in response to: p0p guru
|
|
|
Yeah, it seems there was a .pdf document at the root level of my shared folder that was triggering the problem.
I noticed that after the ATSServer messags in the Console, I'd see this message:
10/18/08 12:44:53 PM quicklookd2656 Notice QL ERROR 'Creating thumbnail' timed out for '<QLThumbnailRequest /Volumes/mike/5513.pdf>'
I moved "5513.pdf" to another location (so it doesn't appear in the Finder window that opens when the "mike" share is mounted on the MacBook), and then I can mount without ATSServer going crazy.
MacBook
Mac OS X (10.5.5)
|
|
Posts:
9
Registered:
Oct 18, 2008
|
|
|
Posts:
1
From:
France
Registered:
Oct 27, 2008
|
|
|
|
Re: ATSServer CPU @ 200% LOCKS-UP Mac Pro dual quad-core desktop
Posted:
Oct 27, 2008 11:17 AM
in response to: agent_of_fortune
|
|
|
Same problem with my G5 Quad under 10.5.5
200% CPU
had to kill the process twice :
sudo killall ATSServer
afterwards all came back to normal
Seems to be a bug in 10.5.5
G5 Quad
Mac OS X (10.5.5)
|
|
Posts:
31
From:
Wisconsin
Registered:
Aug 30, 2005
|
|
|
|
Re: ATSServer CPU @ 200% LOCKS-UP Mac Pro dual quad-core desktop
Posted:
Nov 6, 2008 12:05 AM
in response to: agent_of_fortune
|
|
|
I am having the same difficulty. It all started when I attempted to open a PDF file I had created with a scanner. After that, every time I booted, the system would pretty much lock up. The on-boot behavior ended when I turned off iTunes Helper in the startup folder. However, ATSServer still goes berserk if I attempt to open the PDF file. I am going to download Adobe Reader and see if that works any better.
MacBook Pro dual core
Mac OS X (10.5.5)
|
|
Posts:
31
From:
Wisconsin
Registered:
Aug 30, 2005
|
|
|
|
Re: ATSServer CPU @ 200% LOCKS-UP Mac Pro dual quad-core desktop
Posted:
Nov 6, 2008 8:31 AM
in response to: agent_of_fortune
|
|
|
I downloaded Adobe Reader, and it is working much better than preview for the document I scanned into a PDF (at least it opens it). The system is quite hosed though. It slips into SSBoD mode for no apparent reason, and the menu bar is messed up. The GUI hangs. One can still connect via ssh and "do stuff," but this new system has suddenly gotten into a useless state after a few weeks of nearly flawless operation. I suspect I will have to erase and re-install everything, but there is no point in doing so if it is going to do the same thing over again.
MacBookPro
Mac OS X (10.5.5)
|
|
Posts:
9
Registered:
Nov 8, 2006
|
|
|
|
Re: ATSServer CPU @ 200% LOCKS-UP Mac Pro dual quad-core desktop
Posted:
Nov 6, 2008 8:53 AM
in response to: Richard Bonomo
|
|
|
I wouldn't go for a reinstall. The bug is almost certainly in Quicklook - I only suffer if I look use the Finder to look in folders with OO docs. The system is then irretrievably locked unless I can manually kill the ATServer fast enough. I'd be screwed if I kept a lot of stuff on my Desktop but fortunately I use Documents instead.
We might get lucky in the next patch from Apple but I'm not holding my breath. We're more likely to get 3D album art or other essential "feature" for iTwits.
MacBook
Mac OS X (10.5.5)
|
|
Posts:
31
From:
Wisconsin
Registered:
Aug 30, 2005
|
|
|
|
Re: ATSServer CPU @ 200% LOCKS-UP Mac Pro dual quad-core desktop
Posted:
Nov 6, 2008 8:57 AM
in response to: Charlie_X
|
|
|
FWIW, I just submitted a formal bug report to Apple, as I doubt they read this fora closely.
MacBookPro
Mac OS X (10.5.5)
|
|
Posts:
9
Registered:
Nov 8, 2006
|
|
|
|
Re: ATSServer CPU @ 200% LOCKS-UP Mac Pro dual quad-core desktop
Posted:
Nov 6, 2008 9:02 AM
in response to: Richard Bonomo
|
|
|
I'm sure they probably do monitor it and there have been several bugs submitted but it is always a question of resources and Mac OS hasn't been getting much of them since the iPhone. And I don't think anyone believes they've really reassigned developers since then. Maybe they are working hard on an ARM-based notebook (and I wouldn't mind if they would). Apple's preferred solution is "Buy a new one".
MacBook
Mac OS X (10.5.5)
|
|
|
