Mac OS X isn't supposed to hit filesystem that hard...

[Zarel]

So, on a whim, I did a fs_usage on Warzone.

Code: Select all

isoleucine:~ zarel$ sudo fs_usage Warzone

That's how I learned that Warzone is reading from the Lucida Grande font file 1888 times per second. Compare that to the second heaviest filesystem hitter - Firefox, at around 4 accesses per second. Note that unlike Warzone, Firefox actually uses a cache in the filesystem.

I'm pretty sure this is some bug with the font renderer. Thoughts?

Attached: Three seconds' worth of the output. Warning: Big enough to cause problems with some text editors. The linebreaks are CRLF in case you Windows folk want to see it.

[cybersphinx]

That's probably caused by GLC/fontconfig, not Warzone itself. Do you use the newest versions of those?

[Zarel]

Doubtful; how do I check my versions again?

[-Kosh-]

Doubtful; how do I check my versions again?

Why is that doubtful? Fonts are controlled by fontconfig indirectly by qglc.

[Zarel]

I meant that it's doubtful that I'm using the latest versions. Of course, I was wrong about that, too.

I'm apparently using QGLC 0.7.2, which is the latest stable. As far as I know, it doesn't even use fontconfig on OS X anymore, because the only copy of fontconfig I have right now was installed after the first time I built Warzone. Either way, my version of fontconfig in MacPorts is 2.7.3, which is also the latest version.

Anyone have any ideas for figuring out what's wrong?

[cybersphinx]

First question would be if that only happens on Macs, though maybe fontconfig prevents the file-hitting on other systems. Is there an equivalent to fs_usage for Linux (or Windows)? Or you could look for a quesoglc mailing list or bugtracker to see if someone else reported that problem, and ask there if not.

[Kamaze]

Try processexplorer on windows. It showed that the havy startup-delay on windows was also caused by huge font parsing. There is something really fishy within font-handling.