Bug 98422 - fc-cache failed to generate correct cache for builtin font-set SFNS-series
Summary: fc-cache failed to generate correct cache for builtin font-set SFNS-series
Status: RESOLVED DUPLICATE of bug 97546
Alias: None
Product: fontconfig
Classification: Unclassified
Component: fc-cache (show other bugs)
Version: 2.12
Hardware: x86-64 (AMD64) Mac OS X (All)
: medium critical
Assignee: fontconfig-bugs
QA Contact: Behdad Esfahbod
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-25 02:28 UTC by whitebob
Modified: 2016-10-27 15:30 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
cache problem output (85.72 KB, image/png)
2016-10-25 02:35 UTC, whitebob 		Details
View All

Description whitebob 2016-10-25 02:28:40 UTC 
This bug happens with new Xquartz 2.7.10, with fontconfig  lib 2.12.1
It seems have some problems when cache the system fonts SFNSDislay-* or SFNSText-* in the directory /System/Library/Fonts/.

fc-cache will report an invalid cache file found and then delete it. Thus every time the  fontconfig lib will recache it. This behavior results in a big latency (15s~40s) when launching  program such as xterm and xfontsel. 

I am sure those SFNS-Series otf fonts have some problem with new version fontconfig. 
but not sure it is due to the font file problem or errors from fontconfig.  

Temporary solution is to disable the font path /System/Library/Fonts in /opt/X11/lib/X11/fontconfig/conf.d/05-OSX-fonts.conf

As it is terribly slowing down the launch of xterm and window manager, I mark it as a critical problem, though the problem may be easy to solve.
Comment 1 whitebob 2016-10-25 02:35:09 UTC 
Created attachment 127526 [details]
cache problem output
Comment 2 whitebob 2016-10-25 06:20:06 UTC 
This bug still exists in 2.7.11_rc1.  I doubt it is not the same as bug #97546.
Comment 3 whitebob 2016-10-27 15:30:30 UTC 

*** This bug has been marked as a duplicate of bug 97546 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.