Comment 8 for bug 443010

Remi,

I've now opened a fontconfig bugtask for this issue so that fontconfig experts can review this; I've found http://osdir.com/ml/fonts.fontconfig/2006-02/msg00135.html after short googling, which indicates that fontconfig indeed seems to be not thread safe.

However, in the presented backtrace here I see that only thread 1 is executing code from libfontconfig.so.1. Can you please elaborate what makes you think that this particular crash is a syncronization problem in libfontconfig?