New issue
Advanced search Search tips

Issue 895786 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

ToT Chromium reports issues connecting to font server

Project Member Reported by drott@chromium.org, Oct 16

Issue description

ToT @1871d55669c7d797b31c

starts spewing messages at startup like:

2018-10-16 14:32:13.882 Chromium Helper[80384:269773] XType: failed to connect - Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.fonts was invalidated." UserInfo={NSDebugDescription=The connection to service named com.apple.fonts was invalidated.}
2018-10-16 14:32:13.882 Chromium Helper[80384:269773] Font server protocol version mismatch (expected:5 got:0), falling back to local fonts
2018-10-16 14:32:13.882 Chromium Helper[80384:269773] XType: unable to make a connection to the font daemon!
2018-10-16 14:32:13.882 Chromium Helper[80384:269773] registering /System/Library/Fonts/*, /System/Library/Fonts/Base/*, and /Library/Fonts/* locally
2018-10-16 14:32:13.882 Chromium Helper[80384:269773] XType: unable to find LucidaGrande in registry. This will likely wreak havoc!
2018-10-16 14:32:13.882 Chromium Helper[80384:269773] Could not retrieve fonts from the server! Registering system fonts locally...

I am not yet sure from which process these are coming.


 
I cannot repro this and we haven't made any changes to the sandbox profile recently. It could be that the font server is unhealthy. Maybe try rebooting (or killing fontd, but I find that things don't recover very well when doing that).

Btw, the PIDs are in the log message. So that's coming from pid 80384.

Sign in to add a comment