commit | c22288fbdbcd7a48c66612db70168fa5cdf715dc | [log] [tgz] |
---|---|---|
author | Ben Wagner <bungeman@google.com> | Mon Nov 02 12:15:20 2020 -0500 |
committer | Skia Commit-Bot <skia-commit-bot@chromium.org> | Mon Nov 02 19:58:14 2020 +0000 |
tree | 020a7d43abe0af100090ad67eb5b5e2386d290a9 | |
parent | 753c1b336802dad8666f37cd9419289651382ae4 [diff] |
Declare FontConfig not threadsafe. Some time ago FontConfig stopped being thread antagonistic and documented that it was thread safe (or at least any thread un-safety was a bug). However, until https://gitlab.freedesktop.org/fontconfig/fontconfig/-/commit/447b9ccc7d03bf953d1f1c4708ca16c56c1511ec at least one of the basic atomic primitives was implemented incorrectly. Resume using a mutex to serialize access to FontConfig until 2.13.93. Bug: cl/339089311 Change-Id: I632f03bc575a37b5391390a0868aef256e3aacda Reviewed-on: https://skia-review.googlesource.com/c/skia/+/331339 Reviewed-by: Mike Klein <mtklein@google.com> Commit-Queue: Ben Wagner <bungeman@google.com>