<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Make fontconfig scanning faster"
href="https://bugs.freedesktop.org/show_bug.cgi?id=64766#c18">Comment # 18</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Make fontconfig scanning faster"
href="https://bugs.freedesktop.org/show_bug.cgi?id=64766">bug 64766</a>
from <span class="vcard"><a class="email" href="mailto:lachs0r@srsfckn.biz" title="Martin Herkt <lachs0r@srsfckn.biz>"> <span class="fn">Martin Herkt</span></a>
</span></b>
<pre>Why did this even turn into a debate about whether there are valid use cases
for in-memory font queries? Regardless of that, the matter of fact is that
fontconfig's scanning is slow enough to be a major nuisance to users even if
there are no in-memory fonts - enough to completely break usability on
non-Linux platforms (let me take this moment to remind you of
<a href="http://lists.freedesktop.org/archives/fontconfig/2009-May/003156.html">http://lists.freedesktop.org/archives/fontconfig/2009-May/003156.html</a> since
this still happens very frequently and leads to people claiming that software
crashes on their systems when it's really just fontconfig freezing the thing).
At this point, what fontconfig is used for is completely irrelevant, since the
problem always manifests itself regardless of use case. This is serious enough
that it must be solved by fontconfig/freetype, and the end user or application
that uses fontconfig should not be expected to work around this deficiency.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>