Bug 14424 - FcConfigUptoDate breaks if directory mtime is in the future
Summary: FcConfigUptoDate breaks if directory mtime is in the future
Status: RESOLVED FIXED
Alias: None
Product: fontconfig
Classification: Unclassified
Component: library (show other bugs)
Version: 2.4
Hardware: All All
: medium normal
Assignee: Keith Packard
QA Contact:
URL: http://dev.laptop.org/ticket/6046
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-08 09:28 UTC by Sayamindu Dasgupta
Modified: 2008-05-24 16:15 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Patch to fix FcConfigUptoDate() (951 bytes, patch)
2008-02-08 09:28 UTC, Sayamindu Dasgupta 		Details | Splinter Review
View All

Description Sayamindu Dasgupta 2008-02-08 09:28:57 UTC 
Created attachment 14216 [details] [review]
Patch to fix FcConfigUptoDate()

At OLPC, we came across a bug where the Browse activity (based on xulrunner) took 100% CPU after an upgrade/. It turns out the Mozilla uses FcConfigUptoDate() to check if new fonts have been added to the system, and this function was always returning FcFalse since we have the mtimes of some font directories set in the future. The attached patch makes  FcConfigUptoDate() print a warning and return FcTrue if mtime of directories are in the future.
Comment 1 Keith Packard 2008-05-24 16:15:42 UTC 
Thanks. Applied in ad3fc667914d19435ade56adc8afe584d5605d10.

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.