> Need to check whether these are OS objects, and if so, whether they're > thread safe on all platforms. Linux fontconfig in particular is particularly > bad, as we've discovered. (You need a lock around the whole thing unless you > have a *very* recent version, newer than the one in many distros.) :(
Even if they aren't, we need a limited amount of info and it seems reasonable that we could cache it in the FontList data. I believe this is only used to figure out what specific font we want from a description. Once we have a font list, I don't think we actually need to talk to the OS anymore except to get the specific font. Also, I think you're thinking of Freetype not fontconfig as being thread-unsafe; perhaps they both are, but the issue I remember from recent hsitory was with Freetype. jack. _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
