Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

What is 'fontworker' doing?

1,338 views
Skip to first unread message

Brian Gordon

unread,
Feb 24, 2014, 11:21:54 PM2/24/14
to
Running the latest of everything on a MacBook Pro. System has been real
sluggish all day, and 'top' shows that around half the CPU time is being taken
up by "fontworker". From the man description, I can't see why it would be
running at all, let alone the dominant process.

If I 'kill' it, another instance appears immediately. Rebooting doesn't seem
to help, either. Any suggestions?

--
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
| Brian Gordon -->bri...@panix.com<-- brian dot gordon at cox dot net |
+ briang...@hotmail.com Bass: Lexington "Main Street Harmonizers" chorus +
-------------------------------------------------------------------------------

Jolly Roger

unread,
Mar 1, 2014, 5:09:55 PM3/1/14
to
On 2014-02-25, Brian Gordon <bri...@panix.com> wrote:
> Running the latest of everything on a MacBook Pro. System has been real
> sluggish all day, and 'top' shows that around half the CPU time is being taken
> up by "fontworker". From the man description, I can't see why it would be
> running at all, let alone the dominant process.

Here's the manual page about it:

fontworker(8) BSD System Manager's Manual

NAME
fontworker -- Mac OS X system font registration and validation
daemon

SYNOPSIS
fontworker

DESCRIPTION
fontworker is a system daemon that registers and validates font for
the system.

There are no configuration options to fontworker. Users should not
run fontworker manually.

SEE ALSO
fontd(8)

HISTORY
The fontworker daemon first appeared in MacOS X 10.6.

> If I 'kill' it, another instance appears immediately. Rebooting doesn't seem
> to help, either. Any suggestions?

I would run /Applications/Font Book, select all of your fonts, and
choose File > Validate Fonts from the menu bar to see if there are any
bad fonts installed that may be causing this behavior.

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR
0 new messages